Re: [RFC PATCHv2] usb: USB Type-C Connector Class

On 05/20/2016 06:37 AM, Oliver Neukum wrote: On Fri, 2016-05-20 at 14:24 +0300, Heikki Krogerus wrote: On Thu, May 19, 2016 at 04:47:17PM +0200, Oliver Neukum wrote: Please explain. How does that express DRP but prefered master? Sorry but I'm not sure what you mean here. If the port is

Re: [RFC PATCHv2] usb: USB Type-C Connector Class

On 05/20/2016 06:37 AM, Oliver Neukum wrote: On Fri, 2016-05-20 at 14:24 +0300, Heikki Krogerus wrote: On Thu, May 19, 2016 at 04:47:17PM +0200, Oliver Neukum wrote: Please explain. How does that express DRP but prefered master? Sorry but I'm not sure what you mean here. If the port is

[PATCHv2] support for AD5820 camera auto-focus coil

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone. Signed-off-by: Pavel Machek --- v2: simple cleanups, fix error paths, simplify probe I think it is ready. Please apply :-). diff --git a/drivers/media/i2c/Kconfig b/drivers/media/i2c/Kconfig

[PATCHv2] support for AD5820 camera auto-focus coil

This adds support for AD5820 autofocus coil, found for example in Nokia N900 smartphone. Signed-off-by: Pavel Machek --- v2: simple cleanups, fix error paths, simplify probe I think it is ready. Please apply :-). diff --git a/drivers/media/i2c/Kconfig b/drivers/media/i2c/Kconfig index

Re: [GIT PULL] Driver core update for 4.7-rc1

On Fri, May 20, 2016 at 10:20:19PM -0700, Linus Torvalds wrote: > On Fri, May 20, 2016 at 10:04 PM, Greg KH wrote: > > > > What warnings? I haven't seen any reports of warnings, what .config > > causes them? > > There's tons of them if you just do an allmodconfig

Re: [GIT PULL] Driver core update for 4.7-rc1

On Fri, May 20, 2016 at 10:20:19PM -0700, Linus Torvalds wrote: > On Fri, May 20, 2016 at 10:04 PM, Greg KH wrote: > > > > What warnings? I haven't seen any reports of warnings, what .config > > causes them? > > There's tons of them if you just do an allmodconfig build. > > This suddenly

Re: [tip:perf/urgent] perf/x86/intel/pt: Generate PMI in the STOP region as well

On Tue, May 17, 2016 at 10:40:34AM +0200, Ingo Molnar wrote: > > * Alexander Shishkin wrote: > > > tip-bot for Alexander Shishkin writes: > > > > > Commit-ID: ab92b232ae05c382c3df0e3d6a5c6d16b639ac8c > > > Gitweb: > > >

Re: [tip:perf/urgent] perf/x86/intel/pt: Generate PMI in the STOP region as well

On Tue, May 17, 2016 at 10:40:34AM +0200, Ingo Molnar wrote: > > * Alexander Shishkin wrote: > > > tip-bot for Alexander Shishkin writes: > > > > > Commit-ID: ab92b232ae05c382c3df0e3d6a5c6d16b639ac8c > > > Gitweb: > > > http://git.kernel.org/tip/ab92b232ae05c382c3df0e3d6a5c6d16b639ac8c

[PATCH] f2fs: fix to redirty page if fail to gc data page

From: Chao Yu If we fail to move data page during foreground GC, we should give another chance to writeback that page which was set dirty previously by writer. Signed-off-by: Chao Yu --- fs/f2fs/gc.c | 5 - 1 file changed, 4 insertions(+), 1

[PATCH] f2fs: fix to redirty page if fail to gc data page

From: Chao Yu If we fail to move data page during foreground GC, we should give another chance to writeback that page which was set dirty previously by writer. Signed-off-by: Chao Yu --- fs/f2fs/gc.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/fs/f2fs/gc.c

Re: [GIT PULL] Driver core update for 4.7-rc1

On Fri, May 20, 2016 at 10:04 PM, Greg KH wrote: > > What warnings? I haven't seen any reports of warnings, what .config > causes them? There's tons of them if you just do an allmodconfig build. This suddenly enables a lot of random 16-bit ISA driver crap on x86-64,

Re: [GIT PULL] Driver core update for 4.7-rc1

On Fri, May 20, 2016 at 10:04 PM, Greg KH wrote: > > What warnings? I haven't seen any reports of warnings, what .config > causes them? There's tons of them if you just do an allmodconfig build. This suddenly enables a lot of random 16-bit ISA driver crap on x86-64, and not surprisingly it

Re: [GIT PULL] Driver core update for 4.7-rc1

On Fri, May 20, 2016 at 09:51:18PM -0700, Linus Torvalds wrote: > On Fri, May 20, 2016 at 8:23 PM, Greg KH wrote: > > > > William Breathitt Gray (13): > > base: isa: Remove X86_32 dependency > > isa: Decouple X86_32 dependency from the ISA Kconfig option >

Re: [GIT PULL] Driver core update for 4.7-rc1

On Fri, May 20, 2016 at 09:51:18PM -0700, Linus Torvalds wrote: > On Fri, May 20, 2016 at 8:23 PM, Greg KH wrote: > > > > William Breathitt Gray (13): > > base: isa: Remove X86_32 dependency > > isa: Decouple X86_32 dependency from the ISA Kconfig option > > So I'm going to revert

Re: [GIT PULL] Driver core update for 4.7-rc1

On Fri, May 20, 2016 at 8:23 PM, Greg KH wrote: > > William Breathitt Gray (13): > base: isa: Remove X86_32 dependency > isa: Decouple X86_32 dependency from the ISA Kconfig option So I'm going to revert these unless I get (a) a good reason for them

Re: [GIT PULL] Driver core update for 4.7-rc1

On Fri, May 20, 2016 at 8:23 PM, Greg KH wrote: > > William Breathitt Gray (13): > base: isa: Remove X86_32 dependency > isa: Decouple X86_32 dependency from the ISA Kconfig option So I'm going to revert these unless I get (a) a good reason for them (b) patches to get rid of the

Re: [PATCH] locking/mutex: Set and clear owner using WRITE_ONCE()

On 05/20/2016 09:00 PM, Davidlohr Bueso wrote: On Fri, 20 May 2016, Waiman Long wrote: I think mutex-debug.h also needs similar changes for completeness. Maybe, but given that with debug the wait_lock is unavoidable, doesn't this send the wrong message? Thanks, Davidlohr You are right.

Re: [PATCH] locking/mutex: Set and clear owner using WRITE_ONCE()

On 05/20/2016 09:00 PM, Davidlohr Bueso wrote: On Fri, 20 May 2016, Waiman Long wrote: I think mutex-debug.h also needs similar changes for completeness. Maybe, but given that with debug the wait_lock is unavoidable, doesn't this send the wrong message? Thanks, Davidlohr You are right.

Re: zone_reclaimable() leads to livelock in __alloc_pages_slowpath()

On 2016/05/21 5:28, Oleg Nesterov wrote: > Hello, > > Recently I hit the problem, _sometimes_ the system just hangs in OOM > situation. > Surprisingly, this time OOM-killer is innocent ;) and finally I can reproduce > this more-or-less reliably just running > > #include > #include

Re: zone_reclaimable() leads to livelock in __alloc_pages_slowpath()

On 2016/05/21 5:28, Oleg Nesterov wrote: > Hello, > > Recently I hit the problem, _sometimes_ the system just hangs in OOM > situation. > Surprisingly, this time OOM-killer is innocent ;) and finally I can reproduce > this more-or-less reliably just running > > #include > #include

Re: sem_lock() vs qspinlocks

On 05/20/2016 08:59 PM, Davidlohr Bueso wrote: On Fri, 20 May 2016, Peter Zijlstra wrote: On Fri, May 20, 2016 at 04:47:43PM -0400, Waiman Long wrote: >Similarly, and I know you hate it, but afaict, then semantically >queued_spin_is_contended() ought to be: > >- return

Re: sem_lock() vs qspinlocks

On 05/20/2016 08:59 PM, Davidlohr Bueso wrote: On Fri, 20 May 2016, Peter Zijlstra wrote: On Fri, May 20, 2016 at 04:47:43PM -0400, Waiman Long wrote: >Similarly, and I know you hate it, but afaict, then semantically >queued_spin_is_contended() ought to be: > >- return

Re: [PATCH 1/2] Documentation: add binding description of Rockchip PCIe controller

On 2016/5/20 19:20, Heiko Stuebner wrote: Hi Shawn, Am Freitag, 20. Mai 2016, 18:29:06 schrieb Shawn Lin: This patch add some required and optional properties for Rockchip PCIe controller. Also we add a example for how to use it. Signed-off-by: Shawn Lin ---

Re: [PATCH 1/2] Documentation: add binding description of Rockchip PCIe controller

On 2016/5/20 19:20, Heiko Stuebner wrote: Hi Shawn, Am Freitag, 20. Mai 2016, 18:29:06 schrieb Shawn Lin: This patch add some required and optional properties for Rockchip PCIe controller. Also we add a example for how to use it. Signed-off-by: Shawn Lin ---

Re: [PATCH 2/2] ip6_gre: Set flowi6_proto as IPPROTO_GRE in xmit path.

> On May 21, 2016, at 1:48 AM, David Miller wrote: > > From: Haishuang Yan > Date: Wed, 18 May 2016 18:05:52 +0800 > >> In gre6 xmit path, we are sending a GRE packet, so set fl6 proto >> to IPPROTO_GRE properly. >> >> Signed-off-by:

Re: [PATCH 2/2] ip6_gre: Set flowi6_proto as IPPROTO_GRE in xmit path.

> On May 21, 2016, at 1:48 AM, David Miller wrote: > > From: Haishuang Yan > Date: Wed, 18 May 2016 18:05:52 +0800 > >> In gre6 xmit path, we are sending a GRE packet, so set fl6 proto >> to IPPROTO_GRE properly. >> >> Signed-off-by: Haishuang Yan > > I think it would be a lot better to

[GIT PULL] TTY/Serial Update for 4.7-rc1

Note, you will get a merge error in include/uapi/linux/serial_core.h when merging to your tree, just resolve it so that there is a unique number for each serial driver and all should be fine. The following changes since commit

[GIT PULL] TTY/Serial Update for 4.7-rc1

Note, you will get a merge error in include/uapi/linux/serial_core.h when merging to your tree, just resolve it so that there is a unique number for each serial driver and all should be fine. The following changes since commit

[GIT PULL] Driver core update for 4.7-rc1

The following changes since commit c3b46c73264b03000d1e18b22f5caf63332547c9: Linux 4.6-rc4 (2016-04-17 19:13:32 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/ tags/driver-core-4.7-rc1 for you to fetch changes up to

Re: linux-next: manual merge of the tty tree with Linus' tree

On Fri, May 20, 2016 at 12:31:51PM +1000, Stephen Rothwell wrote: > Hi Greg, > > Today's linux-next merge of the tty tree got a conflict in: > > include/uapi/linux/serial_core.h > > between commits: > > 157b9394709e ("serial: pic32_uart: Add PIC32 UART driver") > 07b75260ebc2 ("Merge

[GIT PULL] Driver core update for 4.7-rc1

The following changes since commit c3b46c73264b03000d1e18b22f5caf63332547c9: Linux 4.6-rc4 (2016-04-17 19:13:32 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/ tags/driver-core-4.7-rc1 for you to fetch changes up to

Re: linux-next: manual merge of the tty tree with Linus' tree

On Fri, May 20, 2016 at 12:31:51PM +1000, Stephen Rothwell wrote: > Hi Greg, > > Today's linux-next merge of the tty tree got a conflict in: > > include/uapi/linux/serial_core.h > > between commits: > > 157b9394709e ("serial: pic32_uart: Add PIC32 UART driver") > 07b75260ebc2 ("Merge

[GIT PULL] Staging driver update for 4.7-rc1

The following changes since commit 44549e8f5eea4e0a41b487b63e616cb089922b99: Linux 4.6-rc7 (2016-05-08 14:38:32 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/ tags/staging-4.7-rc1 for you to fetch changes up to

[GIT PULL] char/misc driver update for 4.7-rc1

The following changes since commit 44549e8f5eea4e0a41b487b63e616cb089922b99: Linux 4.6-rc7 (2016-05-08 14:38:32 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/ tags/char-misc-4.7-rc1 for you to fetch changes up to

[GIT PULL] Staging driver update for 4.7-rc1

The following changes since commit 44549e8f5eea4e0a41b487b63e616cb089922b99: Linux 4.6-rc7 (2016-05-08 14:38:32 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/ tags/staging-4.7-rc1 for you to fetch changes up to

[GIT PULL] char/misc driver update for 4.7-rc1

The following changes since commit 44549e8f5eea4e0a41b487b63e616cb089922b99: Linux 4.6-rc7 (2016-05-08 14:38:32 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/ tags/char-misc-4.7-rc1 for you to fetch changes up to

Re: linux-next 20160512 - ACPI issue with screen brightness

On Fri, May 20, 2016 at 08:15:12PM -0400, valdis.kletni...@vt.edu wrote: > On Fri, 20 May 2016 15:17:20 +0800, Aaron Lu said: > > On Fri, May 20, 2016 at 03:02:08AM -0400, valdis.kletni...@vt.edu wrote: > > > With the patches reverted: > > > > > > [/sys/class/backlight/acpi_video0] grep .

Re: linux-next 20160512 - ACPI issue with screen brightness

On Fri, May 20, 2016 at 08:15:12PM -0400, valdis.kletni...@vt.edu wrote: > On Fri, 20 May 2016 15:17:20 +0800, Aaron Lu said: > > On Fri, May 20, 2016 at 03:02:08AM -0400, valdis.kletni...@vt.edu wrote: > > > With the patches reverted: > > > > > > [/sys/class/backlight/acpi_video0] grep .

[GIT PULL] USB driver update for 4.7-rc1

The following changes since commit 44549e8f5eea4e0a41b487b63e616cb089922b99: Linux 4.6-rc7 (2016-05-08 14:38:32 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/ tags/usb-4.7-rc1 for you to fetch changes up to

[GIT PULL] USB driver update for 4.7-rc1

The following changes since commit 44549e8f5eea4e0a41b487b63e616cb089922b99: Linux 4.6-rc7 (2016-05-08 14:38:32 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/ tags/usb-4.7-rc1 for you to fetch changes up to

Re: [PATCH v2 09/12] clocksource: add J-Core PIT/RTC driver

On Fri, May 20, 2016 at 04:01:56PM +0200, Daniel Lezcano wrote: > On Fri, May 20, 2016 at 02:53:04AM +, Rich Felker wrote: > > Signed-off-by: Rich Felker > > --- > > Hi Rich, > > please add a nice changelog describing how works the timer. OK. Do you prefer this in

Re: [PATCH v2 09/12] clocksource: add J-Core PIT/RTC driver

On Fri, May 20, 2016 at 04:01:56PM +0200, Daniel Lezcano wrote: > On Fri, May 20, 2016 at 02:53:04AM +, Rich Felker wrote: > > Signed-off-by: Rich Felker > > --- > > Hi Rich, > > please add a nice changelog describing how works the timer. OK. Do you prefer this in changelog, comments in

Re: Builtin microcode does nothing..

On 21.05.2016 02:20, Gabriel C wrote: On 20.05.2016 12:08, Gabriel C wrote: Does it work when you disable CONFIG_BLK_DEV_INITRD in there? I can test this when I'm home since I need to change the config a bit. I got to test an kernel without CONFIG_BLK_DEV_INITRD and this way does work.

Re: Builtin microcode does nothing..

On 21.05.2016 02:20, Gabriel C wrote: On 20.05.2016 12:08, Gabriel C wrote: Does it work when you disable CONFIG_BLK_DEV_INITRD in there? I can test this when I'm home since I need to change the config a bit. I got to test an kernel without CONFIG_BLK_DEV_INITRD and this way does work.

Re: [PATCH v8 13/14] usb: gadget: udc: adapt to OTG core

On Fri, May 20, 2016 at 10:26:03AM +0300, Roger Quadros wrote: > Peter, > > On 20/05/16 04:39, Peter Chen wrote: > > On Wed, May 18, 2016 at 03:45:11PM +0300, Roger Quadros wrote: > >> On 18/05/16 06:18, Peter Chen wrote: > >>> On Mon, May 16, 2016 at 12:51:53PM +0300, Roger Quadros wrote: >

Re: [PATCH v8 13/14] usb: gadget: udc: adapt to OTG core

On Fri, May 20, 2016 at 10:26:03AM +0300, Roger Quadros wrote: > Peter, > > On 20/05/16 04:39, Peter Chen wrote: > > On Wed, May 18, 2016 at 03:45:11PM +0300, Roger Quadros wrote: > >> On 18/05/16 06:18, Peter Chen wrote: > >>> On Mon, May 16, 2016 at 12:51:53PM +0300, Roger Quadros wrote: >

[PATCH] iommu/vt-d: reduce extra first level entry in iommu->domains

In commit <8bf478163e69> ("iommu/vt-d: Split up iommu->domains array"), it it splits iommu->domains in two levels. Each first level contains 256 entries of second level. In case of the ndomains is exact a multiple of 256, it would have one more extra first level entry for current implementation.

[PATCH] iommu/vt-d: reduce extra first level entry in iommu->domains

In commit <8bf478163e69> ("iommu/vt-d: Split up iommu->domains array"), it it splits iommu->domains in two levels. Each first level contains 256 entries of second level. In case of the ndomains is exact a multiple of 256, it would have one more extra first level entry for current implementation.

Re: [PATCH v8 13/14] usb: gadget: udc: adapt to OTG core

On Thu, May 19, 2016 at 10:32:44AM +0300, Roger Quadros wrote: > On 18/05/16 17:46, Jun Li wrote: > > > > > > I didn't want to have complex Kconfig so decided to have otg as > built-in only. > What do you want me to change in existing code? and why? > >>> > >>> Remove those

Re: [PATCH v8 13/14] usb: gadget: udc: adapt to OTG core

On Thu, May 19, 2016 at 10:32:44AM +0300, Roger Quadros wrote: > On 18/05/16 17:46, Jun Li wrote: > > > > > > I didn't want to have complex Kconfig so decided to have otg as > built-in only. > What do you want me to change in existing code? and why? > >>> > >>> Remove those

Re: sem_lock() vs qspinlocks

On Fri, May 20, 2016 at 5:48 PM, Davidlohr Bueso wrote: > > I can verify that this patch fixes the issue. Ok, I've applied it to my tree. Linus

Re: sem_lock() vs qspinlocks

On Fri, May 20, 2016 at 5:48 PM, Davidlohr Bueso wrote: > > I can verify that this patch fixes the issue. Ok, I've applied it to my tree. Linus

Re: [PATCH] pinctrl: samsung: Suppress unbinding to prevent theoretical attacks

Hello Krzysztof, On 05/17/2016 02:02 AM, Krzysztof Kozlowski wrote: > Although unbinding a pinctrl driver requires root privileges but it > still might be used theoretically in certain attacks (by triggering NULL > pointer exception or memory corruption). > > Samsung pincontrol drivers are

Re: [PATCH] pinctrl: samsung: Suppress unbinding to prevent theoretical attacks

Hello Krzysztof, On 05/17/2016 02:02 AM, Krzysztof Kozlowski wrote: > Although unbinding a pinctrl driver requires root privileges but it > still might be used theoretically in certain attacks (by triggering NULL > pointer exception or memory corruption). > > Samsung pincontrol drivers are

Re: [PATCH] clk: samsung: Suppress unbinding to prevent theoretical attacks

Hello Krzysztof, On 05/17/2016 03:26 AM, Krzysztof Kozlowski wrote: > Although unbinding a driver requires root privileges but it still might > be used theoretically in certain attacks (by triggering NULL pointer > exception or memory corruption if driver does not provide proper remove >

Re: [PATCH] clk: samsung: Suppress unbinding to prevent theoretical attacks

Hello Krzysztof, On 05/17/2016 03:26 AM, Krzysztof Kozlowski wrote: > Although unbinding a driver requires root privileges but it still might > be used theoretically in certain attacks (by triggering NULL pointer > exception or memory corruption if driver does not provide proper remove >

Re: [PATCH] ARM: exynos: don't select keyboard driver

Hello Arnd, On 05/18/2016 10:17 AM, Arnd Bergmann wrote: > The samsung-keypad driver is implicitly selected by ARCH_EXYNOS4 (why?), > but this fails if CONFIG_INPUT is a loadable module: > > drivers/input/built-in.o: In function `samsung_keypad_remove': >

Re: [PATCH] ARM: exynos: don't select keyboard driver

Hello Arnd, On 05/18/2016 10:17 AM, Arnd Bergmann wrote: > The samsung-keypad driver is implicitly selected by ARCH_EXYNOS4 (why?), > but this fails if CONFIG_INPUT is a loadable module: > > drivers/input/built-in.o: In function `samsung_keypad_remove': >

Re: [PATCH v4] sparc64: Reduce TLB flushes during hugepte changes

From: Nitin Gupta Date: Wed, 30 Mar 2016 11:17:13 -0700 > During hugepage map/unmap, TSB and TLB flushes are currently > issued at every PAGE_SIZE'd boundary which is unnecessary. > We now issue the flush at REAL_HPAGE_SIZE boundaries only. > > Without this patch

Re: [PATCH v4] sparc64: Reduce TLB flushes during hugepte changes

From: Nitin Gupta Date: Wed, 30 Mar 2016 11:17:13 -0700 > During hugepage map/unmap, TSB and TLB flushes are currently > issued at every PAGE_SIZE'd boundary which is unnecessary. > We now issue the flush at REAL_HPAGE_SIZE boundaries only. > > Without this patch workloads which unmap a large

Re: [U-Boot] Sharing code between Linux and bootloader (U-boot) ?

On Fri, May 20, 2016 at 04:28:23PM +0200, Sebastian Frias wrote: > Hi, > > Some bootloaders (like U-boot) support several HW devices: serial, > network, NAND, USB, etc. most of which are also supported by Linux. > > So the question is: is code shared? I mean, I understand that the > drivers

Re: [U-Boot] Sharing code between Linux and bootloader (U-boot) ?

On Fri, May 20, 2016 at 04:28:23PM +0200, Sebastian Frias wrote: > Hi, > > Some bootloaders (like U-boot) support several HW devices: serial, > network, NAND, USB, etc. most of which are also supported by Linux. > > So the question is: is code shared? I mean, I understand that the > drivers

[GIT PULL] clk: changes for v4.7

The following changes since commit 3358d2d9f47af86bdd71edb24b361f72a54ec04e: clk: tegra: Add interface to enable hardware control of SATA/XUSB PLLs (2016-04-28 12:41:44 +0200) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git

[GIT PULL] clk: changes for v4.7

The following changes since commit 3358d2d9f47af86bdd71edb24b361f72a54ec04e: clk: tegra: Add interface to enable hardware control of SATA/XUSB PLLs (2016-04-28 12:41:44 +0200) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git

Re: [PATCH] locking/mutex: Set and clear owner using WRITE_ONCE()

On Fri, 20 May 2016, Waiman Long wrote: I think mutex-debug.h also needs similar changes for completeness. Maybe, but given that with debug the wait_lock is unavoidable, doesn't this send the wrong message? Thanks, Davidlohr

Re: [PATCH] locking/mutex: Set and clear owner using WRITE_ONCE()

On Fri, 20 May 2016, Waiman Long wrote: I think mutex-debug.h also needs similar changes for completeness. Maybe, but given that with debug the wait_lock is unavoidable, doesn't this send the wrong message? Thanks, Davidlohr

Re: sem_lock() vs qspinlocks

On Fri, 20 May 2016, Peter Zijlstra wrote: On Fri, May 20, 2016 at 04:47:43PM -0400, Waiman Long wrote: >Similarly, and I know you hate it, but afaict, then semantically >queued_spin_is_contended() ought to be: > >- return atomic_read(>val) & ~_Q_LOCKED_MASK; >+ return

Re: sem_lock() vs qspinlocks

On Fri, 20 May 2016, Peter Zijlstra wrote: On Fri, May 20, 2016 at 04:47:43PM -0400, Waiman Long wrote: >Similarly, and I know you hate it, but afaict, then semantically >queued_spin_is_contended() ought to be: > >- return atomic_read(>val) & ~_Q_LOCKED_MASK; >+ return

Re: [PATCH] fs: befs: replace GFP_KERNEL by GFP_NOFS

On Fri, May 20, 2016 at 12:07:08PM +0100, Salah Triki wrote: > Since this is a filesystem driver, using the flag GFP_NOFS is more > appropriate than the flag GFP_KERNEL. What does "more appropriate" mean? Either there is a specific reason, or it's a cargo-culting, plain and simple. _Why_ does

Re: [PATCH] fs: befs: replace GFP_KERNEL by GFP_NOFS

On Fri, May 20, 2016 at 12:07:08PM +0100, Salah Triki wrote: > Since this is a filesystem driver, using the flag GFP_NOFS is more > appropriate than the flag GFP_KERNEL. What does "more appropriate" mean? Either there is a specific reason, or it's a cargo-culting, plain and simple. _Why_ does

Re: sem_lock() vs qspinlocks

On Fri, 20 May 2016, Linus Torvalds wrote: Oh, I definitely agree on the stable part, and yes, the "splt things up" model should come later if people agree that it's a good thing. The backporting part is quite nice, yes, but ultimately I think I prefer Linus' suggestion making things

Re: sem_lock() vs qspinlocks

On Fri, 20 May 2016, Linus Torvalds wrote: Oh, I definitely agree on the stable part, and yes, the "splt things up" model should come later if people agree that it's a good thing. The backporting part is quite nice, yes, but ultimately I think I prefer Linus' suggestion making things

Re: [PATCH 3.12 69/76] net: fix infoleak in rtnetlink

On 20.05.2016 18:45, David Miller wrote: > From: Vegard Nossum > Date: Fri, 20 May 2016 14:04:54 +0200 > >> Just out of curiosity, was this observed in practice? I could be >> wrong, but I was under the impression that using designated >> initializers would zero the rest

Re: [PATCH 3.12 69/76] net: fix infoleak in rtnetlink

On 20.05.2016 18:45, David Miller wrote: > From: Vegard Nossum > Date: Fri, 20 May 2016 14:04:54 +0200 > >> Just out of curiosity, was this observed in practice? I could be >> wrong, but I was under the impression that using designated >> initializers would zero the rest of the struct, including

Re: [PATCH v4] platform:x86: Add PMC Driver for Intel Core SOC

On Thu, May 12, 2016 at 6:50 AM, Rajneesh Bhardwaj wrote: > > + * pmc_dev contains info about power management controller device. > + */ > +struct pmc_dev { > + u32 base_addr; > + void __iomem *regmap; > +#if IS_ENABLED(CONFIG_DEBUG_FS) > + struct

Re: [PATCH v4] platform:x86: Add PMC Driver for Intel Core SOC

On Thu, May 12, 2016 at 6:50 AM, Rajneesh Bhardwaj wrote: > > + * pmc_dev contains info about power management controller device. > + */ > +struct pmc_dev { > + u32 base_addr; > + void __iomem *regmap; > +#if IS_ENABLED(CONFIG_DEBUG_FS) > + struct dentry *dbgfs_dir; > +#endif /*

Re: Builtin microcode does nothing..

On 20.05.2016 12:08, Gabriel C wrote: Does it work when you disable CONFIG_BLK_DEV_INITRD in there? I can test this when I'm home since I need to change the config a bit. I got to test an kernel without CONFIG_BLK_DEV_INITRD and this way does work. Regards, Gabriel C

Re: Builtin microcode does nothing..

On 20.05.2016 12:08, Gabriel C wrote: Does it work when you disable CONFIG_BLK_DEV_INITRD in there? I can test this when I'm home since I need to change the config a bit. I got to test an kernel without CONFIG_BLK_DEV_INITRD and this way does work. Regards, Gabriel C

mmotm 2016-05-20-17-11 uploaded

The mm-of-the-moment snapshot 2016-05-20-17-11 has been uploaded to http://www.ozlabs.org/~akpm/mmotm/ mmotm-readme.txt says README for mm-of-the-moment: http://www.ozlabs.org/~akpm/mmotm/ This is a snapshot of my -mm patch queue. Uploaded at random hopefully more than once a week. You

mmotm 2016-05-20-17-11 uploaded

The mm-of-the-moment snapshot 2016-05-20-17-11 has been uploaded to http://www.ozlabs.org/~akpm/mmotm/ mmotm-readme.txt says README for mm-of-the-moment: http://www.ozlabs.org/~akpm/mmotm/ This is a snapshot of my -mm patch queue. Uploaded at random hopefully more than once a week. You

[GIT] Networking

1) Tunneling fixes from Tom Herbert and Alexander Duyck. 2) AF_UNIX updates some struct sock bit fields with the socket lock, whereas setsockopt() sets overlapping ones with locking. Seperate out the synchronized vs. the AF_UNIX unsynchronized ones to avoid corruption. From Andrey

[GIT] Networking

1) Tunneling fixes from Tom Herbert and Alexander Duyck. 2) AF_UNIX updates some struct sock bit fields with the socket lock, whereas setsockopt() sets overlapping ones with locking. Seperate out the synchronized vs. the AF_UNIX unsynchronized ones to avoid corruption. From Andrey

Re: [PATCH] ps3_gelic: use kmemdup

From: Muhammad Falak R Wani Date: Thu, 19 May 2016 19:24:41 +0530 > Use kmemdup when some other buffer is immediately copied into allocated > region. It replaces call to allocation followed by memcpy, by a single > call to kmemdup. > > Signed-off-by: Muhammad Falak R Wani

Re: [PATCH] net:liquidio: use kmemdup

From: Muhammad Falak R Wani Date: Thu, 19 May 2016 19:22:49 +0530 > Use kmemdup when some other buffer is immediately copied into allocated > region. It replaces call to allocation followed by memcpy, by a single > call to kmemdup. > > Signed-off-by: Muhammad Falak R Wani

Re: [PATCH] ps3_gelic: use kmemdup

From: Muhammad Falak R Wani Date: Thu, 19 May 2016 19:24:41 +0530 > Use kmemdup when some other buffer is immediately copied into allocated > region. It replaces call to allocation followed by memcpy, by a single > call to kmemdup. > > Signed-off-by: Muhammad Falak R Wani Applied.

Re: [PATCH] net:liquidio: use kmemdup

From: Muhammad Falak R Wani Date: Thu, 19 May 2016 19:22:49 +0530 > Use kmemdup when some other buffer is immediately copied into allocated > region. It replaces call to allocation followed by memcpy, by a single > call to kmemdup. > > Signed-off-by: Muhammad Falak R Wani Applied.

Re: [PATCH] net: usb: ch9200: use kmemdup

From: Muhammad Falak R Wani Date: Thu, 19 May 2016 19:26:50 +0530 > Use kmemdup when some other buffer is immediately copied into allocated > region. It replaces call to allocation followed by memcpy, by a single > call to kmemdup. > > Signed-off-by: Muhammad Falak R Wani

Re: [PATCH] net: usb: ch9200: use kmemdup

From: Muhammad Falak R Wani Date: Thu, 19 May 2016 19:26:50 +0530 > Use kmemdup when some other buffer is immediately copied into allocated > region. It replaces call to allocation followed by memcpy, by a single > call to kmemdup. > > Signed-off-by: Muhammad Falak R Wani Applied.

Re: pull-request: wireless-drivers-next 2016-05-13 (take two)

From: Kalle Valo Date: Thu, 19 May 2016 15:45:08 +0300 > this the second version of the last pull request to net-next for 4.7, > which got postponed due to the recent iwlwifi merge conflict. Now that > Linus fixed the merge problem in his tree I actually didn't have to fix

Re: pull-request: wireless-drivers-next 2016-05-13 (take two)

From: Kalle Valo Date: Thu, 19 May 2016 15:45:08 +0300 > this the second version of the last pull request to net-next for 4.7, > which got postponed due to the recent iwlwifi merge conflict. Now that > Linus fixed the merge problem in his tree I actually didn't have to fix > anything in my tree

Re: [PATCH net V2] tuntap: correctly wake up process during uninit

From: Jason Wang Date: Thu, 19 May 2016 13:36:51 +0800 > We used to check dev->reg_state against NETREG_REGISTERED after each > time we are woke up. But after commit 9e641bdcfa4e ("net-tun: > restructure tun_do_read for better sleep/wakeup efficiency"), it uses >

Re: [PATCH net V2] tuntap: correctly wake up process during uninit

From: Jason Wang Date: Thu, 19 May 2016 13:36:51 +0800 > We used to check dev->reg_state against NETREG_REGISTERED after each > time we are woke up. But after commit 9e641bdcfa4e ("net-tun: > restructure tun_do_read for better sleep/wakeup efficiency"), it uses > skb_recv_datagram() which does

Re: [PATCH RFC] user-namespaced file capabilities - now with more magic

Quoting Mimi Zohar (zo...@linux.vnet.ibm.com): > On Fri, 2016-05-20 at 14:59 -0500, Serge E. Hallyn wrote: > > Quoting Eric W. Biederman (ebied...@xmission.com): > > > "Serge E. Hallyn" writes: > > > > > > > Quoting Eric W. Biederman (ebied...@xmission.com): > > > >> Mimi Zohar

Re: [PATCH RFC] user-namespaced file capabilities - now with more magic

Quoting Mimi Zohar (zo...@linux.vnet.ibm.com): > On Fri, 2016-05-20 at 14:59 -0500, Serge E. Hallyn wrote: > > Quoting Eric W. Biederman (ebied...@xmission.com): > > > "Serge E. Hallyn" writes: > > > > > > > Quoting Eric W. Biederman (ebied...@xmission.com): > > > >> Mimi Zohar writes: > > > >>

Re: [PATCH net,stable v2] net: cdc_ncm: update datagram size after changing mtu

From: Robert Dobrowolski Date: Thu, 19 May 2016 11:56:09 +0200 > From: Rafal Redzimski > > Current implementation updates the mtu size and notify cdc_ncm > device using USB_CDC_SET_MAX_DATAGRAM_SIZE request about datagram > size

Re: [PATCH net,stable v2] net: cdc_ncm: update datagram size after changing mtu

From: Robert Dobrowolski Date: Thu, 19 May 2016 11:56:09 +0200 > From: Rafal Redzimski > > Current implementation updates the mtu size and notify cdc_ncm > device using USB_CDC_SET_MAX_DATAGRAM_SIZE request about datagram > size change instead of changing rx_urb_size. > > Whenever mtu is

Re: [PATCH RFC] user-namespaced file capabilities - now with more magic

On Fri, 2016-05-20 at 14:59 -0500, Serge E. Hallyn wrote: > Quoting Eric W. Biederman (ebied...@xmission.com): > > "Serge E. Hallyn" writes: > > > > > Quoting Eric W. Biederman (ebied...@xmission.com): > > >> Mimi Zohar writes: > > >> > > >> > On

Re: [PATCH RFC] user-namespaced file capabilities - now with more magic

On Fri, 2016-05-20 at 14:59 -0500, Serge E. Hallyn wrote: > Quoting Eric W. Biederman (ebied...@xmission.com): > > "Serge E. Hallyn" writes: > > > > > Quoting Eric W. Biederman (ebied...@xmission.com): > > >> Mimi Zohar writes: > > >> > > >> > On Thu, 2016-05-19 at 22:40 -0500, Serge E. Hallyn

Re: [PATCH v2 10/12] spi: add driver for J-Core SPI controller

On Fri, May 20, 2016 at 11:23:17AM +0100, Mark Brown wrote: > On Fri, May 20, 2016 at 02:53:04AM +, Rich Felker wrote: > > Signed-off-by: Rich Felker > > --- > > My previous post of the patch series accidentally omitted omitted > > Cc'ing of subsystem maintainers for the

Re: [PATCH v2 10/12] spi: add driver for J-Core SPI controller

On Fri, May 20, 2016 at 11:23:17AM +0100, Mark Brown wrote: > On Fri, May 20, 2016 at 02:53:04AM +, Rich Felker wrote: > > Signed-off-by: Rich Felker > > --- > > My previous post of the patch series accidentally omitted omitted > > Cc'ing of subsystem maintainers for the necessary

  1   2   3   4   5   6   7   8   9   10   >