On 03/21/2018 02:43 PM, Michal Hocko wrote:
> On Wed 21-03-18 14:14:35, Andrey Ryabinin wrote:
>>
>>
>> On 03/20/2018 06:29 PM, Michal Hocko wrote:
>>
Leave all pgdat->flags manipulations to kswapd. kswapd scans the whole
pgdat, so it's reasonable to leave all decisions about node stat
Hi all,
Dne sreda, 21. marec 2018 ob 03:18:13 CET je Icenowy Zheng napisal(a):
> 于 2018年3月21日 GMT+08:00 上午2:46:46, Maxime Ripard
写到:
> >On Sat, Mar 17, 2018 at 01:53:49AM +0800, Icenowy Zheng wrote:
> >> All the sub-blocks of Allwinner A64 DE2 needs the SRAM C on A64
On Wed, Mar 21, 2018 at 09:31:22AM -0700, Yang Shi wrote:
> On 3/21/18 6:08 AM, Michal Hocko wrote:
> > Yes, this definitely sucks. One way to work that around is to split the
> > unmap to two phases. One to drop all the pages. That would only need
> > mmap_sem for read and then tear down the
On 21/03/18 17:12, valmiki wrote:
Hi,
In most of the RP drivers, why two irq chips are being used for MSI ?
One at irq_domain_set_info (which uses irq_compose_msi_msg and
irq_set_affinity methods) and another being registered with struct
msi_domain_info (which uses irq_mask/irq_unmask
On 21 March 2018 at 19:02, Greg Kroah-Hartman
wrote:
> On Tue, Mar 20, 2018 at 11:49:19PM +, Ben Hutchings wrote:
>> On Sun, 2018-03-18 at 11:27 +0100, Greg Kroah-Hartman wrote:
>> > On Sat, Mar 17, 2018 at 03:48:24PM +0530, Naresh Kamboju wrote:
>> [...]
>> > >
Remove ixgbevf_write_tail() in favor of moving writel() close to
wmb().
Signed-off-by: Sinan Kaya
Reviewed-by: Alexander Duyck
---
drivers/net/ethernet/intel/ixgbevf/ixgbevf.h | 5 -
drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c |
Code includes wmb() followed by writel(). writel() already has a barrier
on some architectures like arm64.
This ends up CPU observing two barriers back to back before executing the
register write.
Since code already has an explicit barrier call, changing writel() to
writel_relaxed().
On Wed, 2018-03-21 at 19:06 +, Colin King wrote:
> From: Colin Ian King
>
> The pointer workload is dereferenced before it is null checked, hence
> there is a potential for a null pointer dereference on workload. Fix
> this by only dereferencing workload after it is
Signed-off-by: Mike Rapoport
---
Documentation/vm/page_owner.txt | 34 +-
1 file changed, 21 insertions(+), 13 deletions(-)
diff --git a/Documentation/vm/page_owner.txt b/Documentation/vm/page_owner.txt
index 143..0ed5ab8 100644
---
Signed-off-by: Mike Rapoport
---
Documentation/vm/slub.txt | 357 --
1 file changed, 188 insertions(+), 169 deletions(-)
diff --git a/Documentation/vm/slub.txt b/Documentation/vm/slub.txt
index 8465241..3a775fd 100644
---
Signed-off-by: Mike Rapoport
---
Documentation/vm/pagemap.txt | 164 +++
1 file changed, 89 insertions(+), 75 deletions(-)
diff --git a/Documentation/vm/pagemap.txt b/Documentation/vm/pagemap.txt
index eafcefa..bd6d717 100644
---
Signed-off-by: Mike Rapoport
---
Documentation/vm/page_migration | 149 +---
1 file changed, 77 insertions(+), 72 deletions(-)
diff --git a/Documentation/vm/page_migration b/Documentation/vm/page_migration
index 0478ae2..07b67a8
Signed-off-by: Mike Rapoport
---
Documentation/vm/page_frags | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/Documentation/vm/page_frags b/Documentation/vm/page_frags
index a671456..637cc49 100644
--- a/Documentation/vm/page_frags
+++
Hi Maxime
Please check the TWO points:
1). The mvpp2_prs_flow_find() returns TID if found
The TID=0 is valid FOUND value
For Not-found use -ENOENT (just like your mvpp2_prs_vlan_find)
2). The original code always uses "mvpp2_prs_entry *pe" storage Zero-Allocated
Please check the
On (03/21/18 10:10), Maninder Singh wrote:
> LZ4 specification defines 2 byte offset length for 64 KB data.
> But in case of ZRAM we compress data per page and in most of
> architecture PAGE_SIZE is 4KB. So we can decide offset length based
> on actual offset value. For this we can reserve 1 bit
The A20 supports RGB888 with H/V sync from LCD0. Add a pinmux setting
for the needed pins.
Signed-off-by: Giulio Benetti
---
arch/arm/boot/dts/sun7i-a20.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/sun7i-a20.dtsi
This adds a vendor prefix "micronova" for Micronova srl
Signed-off-by: Giulio Benetti
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
This adds a vendor prefix "cdtech" for CDTech(H.K.) Electronics Limited
Signed-off-by: Giulio Benetti
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git
The A20-Linova1-4_3 HMI, also called Q027_2_A which is printed on
production label, is an industrial Human Machine Interface.
It features:
- 512MB DDR RAM
- 1 Sd-card >= 4GB
- 1 Usb otg(programmable via software) with A-Usb Connector
- 1 Usb host
- 1 Buzzer
- 1 Input for LiPo
- 1 Relay to signal
Signed-off-by: Giulio Benetti
---
.../display/panel/cdtech,s070wv95-ct16.txt | 7 ++
drivers/gpu/drm/panel/panel-simple.c | 27 ++
2 files changed, 34 insertions(+)
create mode 100644
On Wed 21-03-18 12:37:10, David Rientjes wrote:
> On Wed, 21 Mar 2018, Michal Hocko wrote:
>
> > > I'm not sure of the expectation of high-order memcg charging without
> > > __GFP_NORETRY,
> >
> > It should be semantically compatible with the allocation path.
> >
>
> That doesn't make sense,
On 03/21/2018 12:44 PM, Jakob Unterwurzacher wrote:
> On 21.03.18 19:43, John Fastabend wrote:
>> Thats my theory at least. Are you able to test a patch if I generate
>> one to fix this?
>
> Yes, no problem.
Can you try this,
diff --git a/include/net/sch_generic.h b/include/net/sch_generic.h
Bits [47:44] of the TLBI register operand are RES0 for instructions that
require a VA, per the ARM ARM spec, so TLBI operations should avoid writing
non-zero values to these bits.
Signed-off-by: Philip Elcan
---
arch/arm64/include/asm/tlbflush.h | 16 ++--
1
Hello Yan,
On Wed, 21 Mar 2018 19:57:47 +,
Yan Markman wrote :
> Hi Maxime
Please avoid top-posting on this list.
> Please check the TWO points:
>
> 1). The mvpp2_prs_flow_find() returns TID if found
> The TID=0 is valid FOUND value
> For Not-found use
On Wed, 21 Mar 2018, Michal Hocko wrote:
> > That doesn't make sense, the allocation path needs to allocate contiguous
> > memory for the high order, the charging path just needs to charge a number
> > of pages. Why would the allocation and charging path be compatible when
> > one needs to
On 03/18/2018 06:14 PM, Cyrille Pitchen wrote:
> Hi Marek,
Hi,
> Le 18/03/2018 à 00:41, Marek Vasut a écrit :
>> On 03/15/2018 08:04 PM, Cyrille Pitchen wrote:
>>> remove myself as MTD and SPI NOR maintainer.
>>>
>>> Signed-off-by: Cyrille Pitchen
>>
>> What happened
On 21.03.2018 18:16, Robin Murphy wrote:
> On 21/03/18 16:40, Stephen Warren wrote:
>> On 03/21/2018 09:26 AM, Dmitry Osipenko wrote:
>>> On 21.03.2018 17:09, Stefan Agner wrote:
On 21.03.2018 13:13, Robin Murphy wrote:
> On 20/03/18 23:02, Stefan Agner wrote:
>> As documented in GCC
On Wed 21-03-18 14:22:13, David Rientjes wrote:
> On Wed, 21 Mar 2018, Michal Hocko wrote:
>
> > diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> > index d1a917b5b7b7..08accbcd1a18 100644
> > --- a/mm/memcontrol.c
> > +++ b/mm/memcontrol.c
> > @@ -1493,7 +1493,7 @@ static void
[+cc Srinath]
On Wed, Mar 21, 2018 at 05:10:56PM +0100, Marta Rybczynska wrote:
> > On Wed, Mar 21, 2018 at 11:48:09PM +0800, Ming Lei wrote:
> >> On Wed, Mar 21, 2018 at 01:10:31PM +0100, Marta Rybczynska wrote:
> >> > > On Wed, Mar 21, 2018 at 12:00:49PM +0100, Marta Rybczynska wrote:
> >> > >>
Le mercredi 21 mars 2018 à 10:55 +0200, Laurent Pinchart a écrit :
> Hi Nicolas,
>
> On Wednesday, 21 March 2018 05:38:59 EET Nicolas Dufresne wrote:
> > Le mardi 20 mars 2018 à 20:04 +0200, Laurent Pinchart a écrit :
> > > On Tuesday, 20 March 2018 19:45:51 EET Nicolas Dufresne wrote:
> > > > Le
On 21/03/18 11:40 AM, Andy Shevchenko wrote:
> The first patches that I didn't reviewed before makes sense to me, the
> rest (at the end) FWIW,
>
> Reviewed-by: Andy Shevchenko
Great, thanks!
Logan
On Wed, 2018-03-21 at 19:19 +, Colin King wrote:
> From: Colin Ian King
>
> There are three kmalloc allocations that are not null checked which
> potentially could lead to null pointer dereference issues. Fix this
> by adding null pointer return checks.
looks like
On Mon, Mar 19, 2018 at 10:47:45PM -0400, Sinan Kaya wrote:
> diff --git a/drivers/infiniband/hw/i40iw/i40iw_uk.c
> b/drivers/infiniband/hw/i40iw/i40iw_uk.c
> index 8afa5a6..7f0ebed 100644
> +++ b/drivers/infiniband/hw/i40iw/i40iw_uk.c
> @@ -723,7 +723,7 @@ static void
On Wed, Mar 21, 2018 at 08:27:07PM +0100, Matias Bjørling wrote:
> Enable the lightnvm integration to use the nvme_get_log_ext()
> function.
>
> Signed-off-by: Matias Bjørling
Thanks, applied to nvme-4.17.
On Wed, 21 Mar 2018 09:13:14 -0700 Mike Kravetz wrote:
> If System V shmget/shmat operations are used to create a hugetlbfs
> backed mapping, it is possible to munmap part of the mapping and
> split the underlying vma such that it is not huge page aligned.
> This will
On Wed, 2018-03-21 at 09:15 -0400, Steven Rostedt wrote:
> On Wed, 21 Mar 2018 15:37:15 +1100
> Stephen Rothwell wrote:
>
> > Hi all,
> >
> > On Wed, 21 Mar 2018 15:31:27 +1100 Stephen Rothwell
> > wrote:
> > >
> > > Today's linux-next merge of
From: Michal Hocko
David has noticed that THP memcg charge can trigger the oom killer
since 2516035499b9 ("mm, thp: remove __GFP_NORETRY from khugepaged and
madvised allocations"). We have used an explicit __GFP_NORETRY
previously which ruled the OOM killer automagically.
Memcg
On 03/14/2018 10:43 PM, Simon Gaiser wrote:
> Commit fd8aa9095a95 ("xen: optimize xenbus driver for multiple
> concurrent xenstore accesses") made a subtle change to the semantic of
> xenbus_dev_request_and_reply() and xenbus_transaction_end().
>
> Before on an error response to XS_TRANSACTION_END
Fix typo in the words 'receiver', 'specified', 'during'
Signed-off-by: Vasyl Gomonovych
---
drivers/rapidio/rio-scan.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/rapidio/rio-scan.c b/drivers/rapidio/rio-scan.c
index
Abdul Salif ,{ESQ}
Avenue Bassawaga
Ouagadougou, Burkina Faso
Email: (abdul-sa...@consultant.com)
Dear Friend,
Compliments of the day. I hope that this letter does not surprise you
because we have not met. However, I urge you to treat the information
with it's contains with due and utmost
On Wed, Mar 21, 2018 at 12:34 PM, Colin King wrote:
> From: Colin Ian King
>
> The current logic of flags | TUNNEL_SEQ is always non-zero and hence
> sequence numbers are always incremented no matter the setting of the
> TUNNEL_SEQ bit. Fix
On Wed, 21 Mar 2018, Michal Hocko wrote:
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index d1a917b5b7b7..08accbcd1a18 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -1493,7 +1493,7 @@ static void memcg_oom_recover(struct mem_cgroup *memcg)
>
> static void
On Mon, Mar 12, 2018 at 05:13:32PM +0800, Jay Fang wrote:
> PCIe 4.0 provides an effective 16.0 GT/second/lane/direction of raw
> bandwidth. Current PCI driver does not support this new feature.
> For example, when you read a PCIe 4.0 EP's link data rate by sysfs, it
> will return "Unknown speed",
Sorry to dig up an old thread but a coworker was asking about this
patch. This is essentially the code that landed in commit
f2f43e566a02a3bdde0a65e6a2e88d707c212a29 "mm/vmscan.c: fix unsequenced
modification and access warning".
Is .reclaim_idx still correct in the case of try_to_free_pages()?
Current x86 Device Tree implementation does not support multiprocessing.
Use new DT bindings to describe the processors.
Signed-off-by: Ivan Gorinov
---
arch/x86/kernel/devicetree.c | 39 ---
1 file changed, 28 insertions(+), 11
Use the "reg" property to specify the processor's local APIC ID instead of
setting it to the "cpu" node index in Device Tree.
Local APIC ID is assigned by hardware and visible in the APIC ID register.
Some processor models allow APIC ID to be changed by software, but CPUID
instruction executed
On Wed, Mar 21, 2018 at 2:51 PM, wrote:
> On 2018-03-21 17:48, Jeff Kirsher wrote:
>>
>> On Wed, 2018-03-21 at 14:56 -0400, Sinan Kaya wrote:
>>>
>>> Remove ixgbevf_write_tail() in favor of moving writel() close to
>>> wmb().
>>>
>>> Signed-off-by: Sinan Kaya
On Wed, Mar 21, 2018 at 10:50:01AM +0800, Wu Hao wrote:
> On Tue, Mar 20, 2018 at 03:32:34PM -0500, Alan Tull wrote:
> > On Tue, Feb 13, 2018 at 3:24 AM, Wu Hao wrote:
> >
> > Hi Hao,
> >
> > Elsewhere we discussed moving #defines used only in this driver either
> > to this .c
On Wed, Mar 21, 2018 at 02:18:43PM +0100, Greg Kroah-Hartman wrote:
> On Tue, Mar 20, 2018 at 08:50:12AM +0100, Greg Kroah-Hartman wrote:
> > On Mon, Mar 19, 2018 at 07:04:43PM +0100, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 4.4.123 release.
> > > There
On Wed, 2018-03-21 at 09:58 -0700, Stephen Boyd wrote:
> From: Stephen Boyd
>
> Some qcom platforms make some GPIOs or pins unavailable for use by
> non-secure operating systems, and thus reading or writing the
> registers
> for those pins will cause access control issues.
On Tue, Mar 20, 2018 at 09:24:41PM -0700, John Hubbard wrote:
> On 03/19/2018 07:00 PM, jgli...@redhat.com wrote:
> > From: Jérôme Glisse
> >
> > This code was lost in translation at one point. This properly call
> > mmu_notifier_unregister_no_release() once last user is
On Tue, Mar 20, 2018 at 10:48:48AM +0100, Geert Uytterhoeven wrote:
>Hi Sasha,
>
>On Mon, Mar 19, 2018 at 5:12 PM, Sasha Levin
> wrote:
>> From: Michael Schmitz
>>
>> [ Upstream commit 9dfa7bba35ac08a63565d58c454dccb7e1bb0a08 ]
>>
>> get_reg()
On 21 March 2018 9:54:37 PM IST, Greg KH wrote:
>On Wed, Mar 21, 2018 at 09:09:57AM -0700, Vic Wei wrote:
>> QCA Rome controllers can do both LE scan and BR/EDR inquiry at once.
>>
>> Change-Id: I89e1412d635f4cd7b2500f7492f37430ea139f0c
>
>What is this line for?
On Wed, Mar 21, 2018 at 12:11:10PM +0100, 王金浦 wrote:
> 2018-03-21 0:19 GMT+01:00 Ben Hutchings :
> > On Sun, 2018-03-18 at 11:14 +0100, Greg Kroah-Hartman wrote:
> >> On Fri, Mar 16, 2018 at 04:55:37PM -0600, Jerry Hoemann wrote:
> >> >
> >> > Greg,
> >> >
> >> >
Hey Eric,
On Tue, Mar 20, 2018 at 10:20:21AM -0500, Eric W. Biederman wrote:
>Sasha Levin writes:
>
>What is the justification for backporting this and the other similar
>Documentation commits?
It was flagged as a bug fixing patch by a new process we're testing,
[ Adding PeterZ to participants due to query about lockdep_assert() ]
On Wed, Mar 21, 2018 at 8:38 AM, Arnaldo Carvalho de Melo
wrote:
>
> assert_spin_locked(>t_state_lock);
> - WARN_ON_ONCE(!irqs_disabled());
> + WARN_ON_ONCE_NONRT(!irqs_disabled());
Ugh.
Em Wed, Mar 21, 2018 at 05:04:46PM +0100, Jiri Olsa escreveu:
> On Wed, Mar 21, 2018 at 12:43:15PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Wed, Mar 21, 2018 at 12:40:35PM -0300, Arnaldo Carvalho de Melo escreveu:
> > > Em Wed, Mar 21, 2018 at 04:38:07PM +0100, Jiri Olsa escreveu:
> > > > On
From: Colin Ian King
The pointer workload is dereferenced before it is null checked, hence
there is a potential for a null pointer dereference on workload. Fix
this by only dereferencing workload after it is null checked.
Detected by CoverityScan, CID#1466017
Quoting David Collins (2018-03-16 18:09:10)
> diff --git a/drivers/regulator/Kconfig b/drivers/regulator/Kconfig
> index 097f617..e0ecd0a 100644
> --- a/drivers/regulator/Kconfig
> +++ b/drivers/regulator/Kconfig
> @@ -671,6 +671,15 @@ config REGULATOR_QCOM_RPM
> Qualcomm RPM as a
Hi Johannes!
Thank you for review!
I've answered most important questions below.
What about all other stylistic/naming/cosmetic issues, I've no
objections, I'll address them in v2.
> Hi Roman,
>
> On Tue, Mar 20, 2018 at 10:33:53PM +, Roman Gushchin wrote:
> > This patch aims to address an
Signed-off-by: Mike Rapoport
---
Documentation/vm/numa | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/vm/numa b/Documentation/vm/numa
index a31b85b..c81e7c5 100644
--- a/Documentation/vm/numa
+++ b/Documentation/vm/numa
@@ -1,6 +1,10 @@
+.. _numa:
Signed-off-by: Mike Rapoport
---
Documentation/vm/numa_memory_policy.txt | 533 +---
1 file changed, 283 insertions(+), 250 deletions(-)
diff --git a/Documentation/vm/numa_memory_policy.txt
b/Documentation/vm/numa_memory_policy.txt
index
Signed-off-by: Mike Rapoport
---
Documentation/vm/overcommit-accounting | 107 ++---
1 file changed, 57 insertions(+), 50 deletions(-)
diff --git a/Documentation/vm/overcommit-accounting
b/Documentation/vm/overcommit-accounting
index
Signed-off-by: Mike Rapoport
---
Documentation/vm/mmu_notifier.txt | 108 --
1 file changed, 57 insertions(+), 51 deletions(-)
diff --git a/Documentation/vm/mmu_notifier.txt
b/Documentation/vm/mmu_notifier.txt
index 23b4625..47baa1c
Signed-off-by: Mike Rapoport
---
Documentation/vm/idle_page_tracking.txt | 55 +
1 file changed, 36 insertions(+), 19 deletions(-)
diff --git a/Documentation/vm/idle_page_tracking.txt
b/Documentation/vm/idle_page_tracking.txt
index
On 21 March 2018 at 18:48, Greg Kroah-Hartman
wrote:
> On Tue, Mar 20, 2018 at 08:50:12AM +0100, Greg Kroah-Hartman wrote:
>> On Mon, Mar 19, 2018 at 07:04:43PM +0100, Greg Kroah-Hartman wrote:
>> > This is the start of the stable review cycle for the 4.4.123 release.
A release candidate Git v2.17.0-rc1 is now available for testing
at the usual places. It is comprised of 493 non-merge commits
since v2.16.0, contributed by 62 people, 19 of which are new faces.
The tarballs are found at:
https://www.kernel.org/pub/software/scm/git/testing/
The following
On (03/21/18 10:10), Maninder Singh wrote:
> diff --git a/lib/lz4/lz4_compress.c b/lib/lz4/lz4_compress.c
> index cc7b6d4..185c358 100644
> --- a/lib/lz4/lz4_compress.c
> +++ b/lib/lz4/lz4_compress.c
> @@ -183,7 +183,8 @@ static FORCE_INLINE int LZ4_compress_generic(
> const tableType_t
On Wed, Mar 21, 2018 at 02:49:25PM -0500, Eric W. Biederman wrote:
>Sasha Levin writes:
>
>> Hey Eric,
>>
>> On Tue, Mar 20, 2018 at 10:20:21AM -0500, Eric W. Biederman wrote:
>>>Sasha Levin writes:
>>>
>>>What is the justification
Quoting Andy Shevchenko (2018-03-21 10:59:10)
> On Wed, 2018-03-21 at 09:58 -0700, Stephen Boyd wrote:
> > From: Stephen Boyd
> >
> > Some qcom platforms make some GPIOs or pins unavailable for use by
> > non-secure operating systems, and thus reading or writing the
> >
Hi Stephan,
Thanks for the review,
> -Original Message-
> From: Stephen Boyd [mailto:sb...@kernel.org]
> Sent: Monday, March 19, 2018 1:10 PM
> To: Jolly Shah ; linux-...@vger.kernel.org;
> mark.rutl...@arm.com; michal.si...@xilinx.com; mturque...@baylibre.com;
>
On Wed, 2018-03-21 at 12:59 -0700, Stephen Boyd wrote:
> Quoting Andy Shevchenko (2018-03-21 10:59:10)
> > On Wed, 2018-03-21 at 09:58 -0700, Stephen Boyd wrote:
> > >
> >
> > > + gpiochip->valid_mask = kcalloc(BITS_TO_LONGS(gpiochip-
> > > > ngpio),
> > >
> > > +
On 3/21/2018 3:02 PM, Jason Gunthorpe wrote:
> On Mon, Mar 19, 2018 at 10:47:45PM -0400, Sinan Kaya wrote:
>> diff --git a/drivers/infiniband/hw/i40iw/i40iw_uk.c
>> b/drivers/infiniband/hw/i40iw/i40iw_uk.c
>> index 8afa5a6..7f0ebed 100644
>> +++ b/drivers/infiniband/hw/i40iw/i40iw_uk.c
>> @@
On Mon, Mar 19, 2018 at 08:04:34PM +0200, Ido Schimmel wrote:
>On Mon, Mar 19, 2018 at 03:48:00PM +, Sasha Levin wrote:
>> From: Ido Schimmel
>>
>> [ Upstream commit 5609b80a37f69f796548339e675256188b29c17d ]
>>
>> It is valid to install routes with a nexthop device that
On 2018-03-21 00:08, Linus Torvalds wrote:
> On Tue, Mar 20, 2018 at 3:13 PM, Uecker, Martin
> wrote:
>>
>> here is an idea:
>
> That's not "an idea".
>
> That is either genius, or a seriously diseased mind.
>
> I can't quite tell which.
>
>> a test for
On Wed 21-03-18 10:16:41, Yang Shi wrote:
>
>
> On 3/21/18 9:50 AM, Yang Shi wrote:
> >
> >
> > On 3/21/18 6:14 AM, Michal Hocko wrote:
> > > On Wed 21-03-18 05:31:19, Yang Shi wrote:
> > > > When running some mmap/munmap scalability tests with large memory (i.e.
> > > > > 300GB), the below
Current x86 implementation of Device Tree does not support multiprocessing,
and the bindings documentation describes the "reg" property as CPU number
instead of hardware-assigned local APIC ID.
v7:
* Change log update
v6:
* Calling of_property_read_u32() to get Local APIC ID from "reg"
* DT
On 03/20/18 17:36, Andy Lutomirski wrote:
>>
>> But we also don't need swapgs when we have rdgsbase/wrgsbase available.
>> We can indeed just unconditionally save it (via rdgsbase) into the stack
>> frame and wrgsbase the correct percpu value. In that case it might be
>> necessary in order to
On 03/21/18 20:24, Andy Shevchenko wrote:
> On Wed, Mar 21, 2018 at 8:48 PM, Kirill Marinushkin
> wrote:
>> In the current implementation, `rmmod snd_bcm2835` does not release
>> resources properly. It causes an oops when trying to list sound devices.
>>
>> This commit
Sasha Levin writes:
> Hey Eric,
>
> On Tue, Mar 20, 2018 at 10:20:21AM -0500, Eric W. Biederman wrote:
>>Sasha Levin writes:
>>
>>What is the justification for backporting this and the other similar
>>Documentation commits?
>
> It
ALPS v3 and v7 packet formats reports trackstick pressure. This information
is already parsed in unused "z" variable.
ALPS SS4 S2 devices already reports trackstick pressure as ABS_PRESSURE
attribute, therefore reports pressure in the same way also for v3 and v7.
This patch also updates parsing
On Wed, 2018-03-21 at 13:04 -0700, Stephen Boyd wrote:
> Quoting Andy Shevchenko (2018-03-21 11:07:09)
> > On Wed, 2018-03-21 at 09:58 -0700, Stephen Boyd wrote:
> > >
> Or ternary?
>
> return gpiochip_line_is_valid(chip, offset) ? 0 : -EINVAL;
Fine with me!
--
Andy Shevchenko
On 03/15/2018 10:22 AM, Joao Martins wrote:
> All uploaded PM data from non-dom0 CPUs takes the info from vCPU 0 and
> changing only the acpi_id. For processors which P-state coordination type
> is HW_ALL (0xFD) it is OK to upload bogus P-state dependency information
> (_PSD), because Xen will
On 03/19/2018 12:58 PM, Jason Andryuk wrote:
> Commit 2cc42bac1c79 ("x86-64/Xen: eliminate W+X mappings") introduced a
> call to get_cpu_cap, which is fstack-protected. This is works on x86-64
> as commit 4f277295e54c ("x86/xen: init %gs very early to avoid page
> faults with stack protector")
El Tue, Mar 20, 2018 at 09:45:07PM -0500 Josh Poimboeuf ha dit:
> On Mon, Mar 19, 2018 at 04:22:55PM -0700, Matthias Kaehlcke wrote:
> > arch/x86/mm/pti.o: warning: objtool: pti_init() falls through to next
> > function pti_user_pagetable_walk_pmd()
> > s/debugfs/file.o: warning: objtool:
On Wed, 2018-03-21 at 14:56 -0400, Sinan Kaya wrote:
> Remove ixgbevf_write_tail() in favor of moving writel() close to
> wmb().
>
> Signed-off-by: Sinan Kaya
> Reviewed-by: Alexander Duyck
> ---
> drivers/net/ethernet/intel/ixgbevf/ixgbevf.h
* Pavel Machek [180321 20:32]:
> Hi!
>
> > > Maybe get somebody to help you locally with the debug cable
> > > soldering? :)
> >
> > I suppose people from your hackerspace can help you. It's really
> > easy to do. Soldering can be avoided btw. You can just use a pair
> > of
Signed-off-by: Giulio Benetti
---
.../display/panel/cdtech,s043wq26h-ct7.txt | 7 ++
drivers/gpu/drm/panel/panel-simple.c | 28 ++
2 files changed, 35 insertions(+)
create mode 100644
The A20-Linova1-7 HMI, also called Q027_2_F which is printed on production
label, is an industrial Human Machine Interface.
It features:
- 512MB DDR RAM
- 1 Sd-card >= 4GB
- 1 Usb otg(programmable via software) with A-Usb Connector
- 1 Usb host
- 1 Buzzer
- 1 Input for LiPo
- 1 Relay to signal
Quoting Andy Shevchenko (2018-03-21 11:07:09)
> On Wed, 2018-03-21 at 09:58 -0700, Stephen Boyd wrote:
> > +static int msm_pinmux_request(struct pinctrl_dev *pctldev, unsigned
> > offset)
> > +{
> > + struct msm_pinctrl *pctrl = pinctrl_dev_get_drvdata(pctldev);
> > + struct gpio_chip
Bits for M, R and L buttons are already processed in alps. Other newly
documented bits not yet.
Signed-off-by: Pali Rohár
---
This is based on information which Masaki Ota provided to us.
---
Documentation/input/devices/alps.rst | 7 +--
1 file changed, 5
Quoting Stephen Boyd (2018-03-21 09:58:48)
> + ret = device_property_read_u16_array(pctrl->dev, "gpios", NULL, 0);
> + if (ret > 0 && ret < max_gpios) {
> + u16 *tmp;
> +
> + len = ret;
> + tmp = kmalloc_array(len, sizeof(tmp[0]), GFP_KERNEL);
Hi!
> > Maybe get somebody to help you locally with the debug cable
> > soldering? :)
>
> I suppose people from your hackerspace can help you. It's really
> easy to do. Soldering can be avoided btw. You can just use a pair
> of scissors to cut a USB -> Micro USB cable and use a knife to remove
>
On Wed, Mar 21, 2018 at 9:11 AM, Dmitry Vyukov wrote:
>
> syzkaller/syzbot dashboard is now live at:
> https://syzkaller.appspot.com
Ok, this may well be the thing that makes syzbot reports useful, if
they point to an external report instead of sending an absolutely huge
There are two ways to connect the Steam Controller: directly to the USB
or with the USB wireless adapter. Both methods are similar, but the
wireless adapter can connect up to 4 devices at the same time.
The wired device will appear as 3 interfaces: a virtual mouse, a virtual
keyboard and a
On 21/03/2018 at 16:35:49 +0100, Peter Rosin wrote:
> Hi!
>
> I noticed a *LOT* of pointless pullups and missing pullups related
> to uart/usart pins. These patches fixes what I found.
>
> I separated out the two changes that had pullup on neither rx nor tx,
> since there might exist some reason
This is a RFC for the problem of how to work with the Steam Controller from
a kernel driver without disturbing the user mode drivers.
The main user mode driver is the Steam Controller itself. From now on I will
call any user mode driver a "hidraw client" because that is the mode most of
them use.
> On 21 Mar 2018, at 20.27, Matias Bjørling wrote:
>
>> On 03/21/2018 03:36 PM, Keith Busch wrote:
>> On Wed, Mar 21, 2018 at 03:06:05AM -0700, Matias Bjørling wrote:
outside of nvme core so that we can use it form lightnvm.
Signed-off-by: Javier González
Benjamin,
On Wed, Mar 21, 2018 at 12:32 AM, Benjamin Warnke
<4bwar...@informatik.uni-hamburg.de> wrote:
> Ok, I will use
>
> /* SPDX-License-Identifier: GPL-2.0 */
> /*
> * Copyright (c) 2018 Benjamin Warnke <4bwar...@informatik.uni-hamburg.de>
> ...
>
> at the top of my files instead of that
On 03/21/2018 03:02 PM, Quentin Perret wrote:
> On Wednesday 21 Mar 2018 at 12:26:21 (+), Patrick Bellasi wrote:
>> On 21-Mar 10:04, Juri Lelli wrote:
>>> Hi,
>>>
>>> On 20/03/18 09:43, Dietmar Eggemann wrote:
From: Quentin Perret
[...]
>> Actually I think that
1 - 100 of 1866 matches
Mail list logo