[PATCH -next] media: ov5670: add depends to fix build errors

ot;Rapolu, Chiranjeevi" <chiranjeevi.rap...@intel.com> Cc: "Yang, Hyungwoo" <hyungwoo.y...@intel.com> --- drivers/media/i2c/Kconfig |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- linux-next-20170720.orig/drivers/media/i2c/Kconfig +++ linux-next-2017

[PATCH -next] media: ov5670: add depends to fix build errors

" --- drivers/media/i2c/Kconfig |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- linux-next-20170720.orig/drivers/media/i2c/Kconfig +++ linux-next-20170720/drivers/media/i2c/Kconfig @@ -618,7 +618,7 @@ config VIDEO_OV6650 config VIDEO_OV5670 tristate "OmniVisio

Re: commit 16ecba59 breaks 82574L under heavy load.

On 2017/07/20 10:00, Lennart Sorensen wrote: > On Wed, Jul 19, 2017 at 05:07:47PM -0700, Benjamin Poirier wrote: > > Are you sure about this? In my testing, while triggering the overrun > > with the msleep, I read ICR when entering e1000_msix_other() and RXO is > > consistently set. > > I had

Re: commit 16ecba59 breaks 82574L under heavy load.

On 2017/07/20 10:00, Lennart Sorensen wrote: > On Wed, Jul 19, 2017 at 05:07:47PM -0700, Benjamin Poirier wrote: > > Are you sure about this? In my testing, while triggering the overrun > > with the msleep, I read ICR when entering e1000_msix_other() and RXO is > > consistently set. > > I had

Re: [PATCH][V2] dvb_frontend: ensure that inital front end status initialized

Em Thu, 20 Jul 2017 23:12:07 +0100 Colin King escreveu: > From: Colin Ian King > > The fe_status variable s is not initialized meaning it can have any > random garbage status. This could be problematic if fe->ops.tune is > false as s is not

Re: [PATCH][V2] dvb_frontend: ensure that inital front end status initialized

Em Thu, 20 Jul 2017 23:12:07 +0100 Colin King escreveu: > From: Colin Ian King > > The fe_status variable s is not initialized meaning it can have any > random garbage status. This could be problematic if fe->ops.tune is > false as s is not updated by the call to fe->ops.tune() and a >

[BUG] lockdep splat with cpu_hotplug_lock

My tests triggered this splat on 4.13-rc1: Loading iSCSI transport class v2.0-870. QLogic NetXtreme II iSCSI Driver bnx2i v2.7.10.1 (Jul 16, 2014) iscsi: registered transport (bnx2i) WARNING: possible recursive locking detected 4.13.0-rc1-test+ #2 Not

[BUG] lockdep splat with cpu_hotplug_lock

My tests triggered this splat on 4.13-rc1: Loading iSCSI transport class v2.0-870. QLogic NetXtreme II iSCSI Driver bnx2i v2.7.10.1 (Jul 16, 2014) iscsi: registered transport (bnx2i) WARNING: possible recursive locking detected 4.13.0-rc1-test+ #2 Not

Re: [PATCH][V2] dvb_frontend: ensure that inital front end status initialized

On 07/20/2017 04:12 PM, Colin King wrote: > From: Colin Ian King > > The fe_status variable s is not initialized meaning it can have any > random garbage status. This could be problematic if fe->ops.tune is > false as s is not updated by the call to fe->ops.tune() and

Re: [PATCH][V2] dvb_frontend: ensure that inital front end status initialized

On 07/20/2017 04:12 PM, Colin King wrote: > From: Colin Ian King > > The fe_status variable s is not initialized meaning it can have any > random garbage status. This could be problematic if fe->ops.tune is > false as s is not updated by the call to fe->ops.tune() and a > subsequent check on

Re: [PATCH] lib/int_sqrt.c: Optimize square root function

On Thu, Jul 20, 2017 at 3:34 PM, Peter Zijlstra wrote: >> >> "Why does this matter, and what is the range it matters for?" > > I was looking to do some work on the idle estimator. Parts of that keep > online avg and variance for normal distributions. I wanted to bias the >

Re: [PATCH] lib/int_sqrt.c: Optimize square root function

On Thu, Jul 20, 2017 at 3:34 PM, Peter Zijlstra wrote: >> >> "Why does this matter, and what is the range it matters for?" > > I was looking to do some work on the idle estimator. Parts of that keep > online avg and variance for normal distributions. I wanted to bias the > avg downwards, the way

Re: Makefile:541: arch/avr32/Makefile: No such file or directory

On 07/20/2017 04:18 PM, kbuild test robot wrote: > Hi Hans-Christian, > > FYI, the error/warning still remains. > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > master > head: beaec533fc2701a28a4d667f67c9f59c6e4e0d13 > commit:

Re: Makefile:541: arch/avr32/Makefile: No such file or directory

On 07/20/2017 04:18 PM, kbuild test robot wrote: > Hi Hans-Christian, > > FYI, the error/warning still remains. > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > master > head: beaec533fc2701a28a4d667f67c9f59c6e4e0d13 > commit:

Re: [PATCH] selftests/vm: Add test to validate mirror functionality with mremap

On 07/20/2017 02:36 AM, Anshuman Khandual wrote: > This adds a test to validate mirror functionality with mremap() > system call on shared anon mappings. > > Suggested-by: Mike Kravetz > Signed-off-by: Anshuman Khandual > --- >

Re: [PATCH] selftests/vm: Add test to validate mirror functionality with mremap

On 07/20/2017 02:36 AM, Anshuman Khandual wrote: > This adds a test to validate mirror functionality with mremap() > system call on shared anon mappings. > > Suggested-by: Mike Kravetz > Signed-off-by: Anshuman Khandual > --- > tools/testing/selftests/vm/Makefile| 1 + >

Makefile:541: arch/avr32/Makefile: No such file or directory

Hi Hans-Christian, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: beaec533fc2701a28a4d667f67c9f59c6e4e0d13 commit: 26202873bb51fafdaa51be3e8de7aab9beb49f70 avr32: remove support for AVR32 architecture date: 3

Makefile:541: arch/avr32/Makefile: No such file or directory

Hi Hans-Christian, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: beaec533fc2701a28a4d667f67c9f59c6e4e0d13 commit: 26202873bb51fafdaa51be3e8de7aab9beb49f70 avr32: remove support for AVR32 architecture date: 3

[GIT] Networking

1) BPF verifier signed/unsigned value tracking fix, from Daniel Borkmann, Edward Cree, and Josef Bacik. 2) Fix memory allocation length when setting up calls to ->ndo_set_mac_address, from Cong Wang. 3) Add a new cxgb4 device ID, from Ganesh Goudar. 4) Fix FIB refcount handling, we have

[GIT] Networking

1) BPF verifier signed/unsigned value tracking fix, from Daniel Borkmann, Edward Cree, and Josef Bacik. 2) Fix memory allocation length when setting up calls to ->ndo_set_mac_address, from Cong Wang. 3) Add a new cxgb4 device ID, from Ganesh Goudar. 4) Fix FIB refcount handling, we have

Re: [PATCH] documentation: Fix two-CPU control-dependency example

On Fri, Jul 21, 2017 at 07:52:03AM +0900, Akira Yokosawa wrote: > On 2017/07/20 14:42:34 -0700, Paul E. McKenney wrote: > > On Fri, Jul 21, 2017 at 06:12:56AM +0900, Akira Yokosawa wrote: > >> On 2017/07/20 09:11:52AM -0700, Paul E. McKenney wrote: > >>> On Thu, Jul 20, 2017 at 09:55:31PM +0900,

[PATCH 3/3] arm64: allwinner: a64: add proper support for the Wi-Fi on BPi M64

BPi M64 has an AP6212 Wi-Fi/Bluetooth combo module, and the Wi-Fi SDIO card is connected to the mmc1 controller. The pwrseq of the mmc1 (used to reset the card) used to missing, and the out-of-band interrupt line of the card is not specified. Fix these issues for proper Wi-Fi support of BPi M64.

Re: [PATCH] documentation: Fix two-CPU control-dependency example

On Fri, Jul 21, 2017 at 07:52:03AM +0900, Akira Yokosawa wrote: > On 2017/07/20 14:42:34 -0700, Paul E. McKenney wrote: > > On Fri, Jul 21, 2017 at 06:12:56AM +0900, Akira Yokosawa wrote: > >> On 2017/07/20 09:11:52AM -0700, Paul E. McKenney wrote: > >>> On Thu, Jul 20, 2017 at 09:55:31PM +0900,

[PATCH 3/3] arm64: allwinner: a64: add proper support for the Wi-Fi on BPi M64

BPi M64 has an AP6212 Wi-Fi/Bluetooth combo module, and the Wi-Fi SDIO card is connected to the mmc1 controller. The pwrseq of the mmc1 (used to reset the card) used to missing, and the out-of-band interrupt line of the card is not specified. Fix these issues for proper Wi-Fi support of BPi M64.

[PATCH 2/3] arm64: allwinner: a64: enable AXP803 for Banana Pi M64

Banana Pi M64 board uses an AXP803 PMIC. Enable the PMIC and its regulators. As we have now proper regulators support, missing or dummy regulators are changed to the correct ones. Signed-off-by: Icenowy Zheng --- .../boot/dts/allwinner/sun50i-a64-bananapi-m64.dts | 116

[PATCH 2/3] arm64: allwinner: a64: enable AXP803 for Banana Pi M64

Banana Pi M64 board uses an AXP803 PMIC. Enable the PMIC and its regulators. As we have now proper regulators support, missing or dummy regulators are changed to the correct ones. Signed-off-by: Icenowy Zheng --- .../boot/dts/allwinner/sun50i-a64-bananapi-m64.dts | 116 +++--

[PATCH 1/3] arm64: allwinner: a64: enable USB host controller for BPi M64

Banana Pi M64 connects the USB host-only controller on A64 SoC to a USB hub, which provided the two USB Type-A ports on the board. Enable the USB host controller. The OTG function of the Micro-USB port needs the drivevbus function of the AXP803 driver implemented, so it's not enabled now.

[PATCH 1/3] arm64: allwinner: a64: enable USB host controller for BPi M64

Banana Pi M64 connects the USB host-only controller on A64 SoC to a USB hub, which provided the two USB Type-A ports on the board. Enable the USB host controller. The OTG function of the Micro-USB port needs the drivevbus function of the AXP803 driver implemented, so it's not enabled now.

Re: Modern Suspend on Dell Latitude 5285 does not resume

On Fri, Jul 21, 2017 at 12:41 AM, Nico Schottelius wrote: > > Good evening Mario, > >> Currently the patch does not look at anything in the system to default to >> S2I vs S3. >> This will affect systems that offer S3 and S2I (even if S3 is broken). >> >> Have you

Re: Modern Suspend on Dell Latitude 5285 does not resume

On Fri, Jul 21, 2017 at 12:41 AM, Nico Schottelius wrote: > > Good evening Mario, > >> Currently the patch does not look at anything in the system to default to >> S2I vs S3. >> This will affect systems that offer S3 and S2I (even if S3 is broken). >> >> Have you configured /sys/power/mem_sleep

Re: cpuidle and cpufreq coupling?

On 07/20/2017 02:23 AM, Sudeep Holla wrote: > > > On 20/07/17 08:18, Viresh Kumar wrote: >> On 20-07-17, 01:17, Rafael J. Wysocki wrote: >>> On Thu, Jul 20, 2017 at 12:54 AM, Florian Fainelli >>> wrote: Hi, We have a particular ARM CPU design that is

Re: cpuidle and cpufreq coupling?

On 07/20/2017 02:23 AM, Sudeep Holla wrote: > > > On 20/07/17 08:18, Viresh Kumar wrote: >> On 20-07-17, 01:17, Rafael J. Wysocki wrote: >>> On Thu, Jul 20, 2017 at 12:54 AM, Florian Fainelli >>> wrote: Hi, We have a particular ARM CPU design that is drawing quite a lot of

[RFC PATCH 5/5] ima: Add ns_mnt, dev, ino fields to IMA audit measurement msgs

From: Guilherme Magalhaes Extending audit measurement record with mount namespace id, file inode, and device name. These fields uniquely identify a pathname considering different mount namespaces. The file inode on a given device is unique and these fields are

[RFC PATCH 5/5] ima: Add ns_mnt, dev, ino fields to IMA audit measurement msgs

From: Guilherme Magalhaes Extending audit measurement record with mount namespace id, file inode, and device name. These fields uniquely identify a pathname considering different mount namespaces. The file inode on a given device is unique and these fields are required to identify a namespace id

[RFC PATCH 3/5] ima: mamespace audit status flags

The iint cache stores whether the file is measured, appraised, audited etc. This patch moves the IMA_AUDITED flag into the per-namespace ns_status, enabling IMA audit mechanism to audit the same file each time it is accessed in a new namespace. The ns_status is not looked up if the CONFIG_IMA_NS

[RFC PATCH 3/5] ima: mamespace audit status flags

The iint cache stores whether the file is measured, appraised, audited etc. This patch moves the IMA_AUDITED flag into the per-namespace ns_status, enabling IMA audit mechanism to audit the same file each time it is accessed in a new namespace. The ns_status is not looked up if the CONFIG_IMA_NS

[RFC PATCH 4/5] ima: differentiate auditing policy rules from "audit" actions

From: Mimi Zohar The AUDIT_INTEGRITY_RULE is used for auditing IMA policy rules and the IMA "audit" policy action. This patch defines AUDIT_INTEGRITY_POLICY to reflect the IMA policy rules. Signed-off-by: Mimi Zohar ---

Re: cpuidle and cpufreq coupling?

On 07/20/2017 07:45 AM, Peter Zijlstra wrote: > On Thu, Jul 20, 2017 at 11:52:41AM +0200, Rafael J. Wysocki wrote: >> On Thu, Jul 20, 2017 at 9:18 AM, Viresh Kumar >> wrote: >>> On 20-07-17, 01:17, Rafael J. Wysocki wrote: On Thu, Jul 20, 2017 at 12:54 AM, Florian

[RFC PATCH 4/5] ima: differentiate auditing policy rules from "audit" actions

From: Mimi Zohar The AUDIT_INTEGRITY_RULE is used for auditing IMA policy rules and the IMA "audit" policy action. This patch defines AUDIT_INTEGRITY_POLICY to reflect the IMA policy rules. Signed-off-by: Mimi Zohar --- include/uapi/linux/audit.h | 3 ++-

Re: cpuidle and cpufreq coupling?

On 07/20/2017 07:45 AM, Peter Zijlstra wrote: > On Thu, Jul 20, 2017 at 11:52:41AM +0200, Rafael J. Wysocki wrote: >> On Thu, Jul 20, 2017 at 9:18 AM, Viresh Kumar >> wrote: >>> On 20-07-17, 01:17, Rafael J. Wysocki wrote: On Thu, Jul 20, 2017 at 12:54 AM, Florian Fainelli wrote:

[RFC PATCH 2/5] ima: Add ns_status for storing namespaced iint data

This patch adds an rbtree to the IMA namespace structure that stores a namespaced version of iint->flags in ns_status struct. Similar to the integrity_iint_cache, both the iint ns_struct are looked up using the inode pointer value. The lookup, allocate, and insertion code is also similar, except

[RFC PATCH 2/5] ima: Add ns_status for storing namespaced iint data

This patch adds an rbtree to the IMA namespace structure that stores a namespaced version of iint->flags in ns_status struct. Similar to the integrity_iint_cache, both the iint ns_struct are looked up using the inode pointer value. The lookup, allocate, and insertion code is also similar, except

[RFC PATCH 1/5] ima: extend clone() with IMA namespace support

From: Yuqiong Sun Add new CONFIG_IMA_NS config option. Let clone() create a new IMA namespace upon CLONE_NEWNS flag. Add ima_ns data structure in nsproxy. ima_ns is allocated and freed upon IMA namespace creation and exit. Currently, the ima_ns contains no useful IMA data but

[RFC PATCH 1/5] ima: extend clone() with IMA namespace support

From: Yuqiong Sun Add new CONFIG_IMA_NS config option. Let clone() create a new IMA namespace upon CLONE_NEWNS flag. Add ima_ns data structure in nsproxy. ima_ns is allocated and freed upon IMA namespace creation and exit. Currently, the ima_ns contains no useful IMA data but only a dummy

Re: [PATCH v6 0/2] x86: Implement fast refcount overflow protection

On Thu, Jul 20, 2017 at 10:15 AM, Kees Cook wrote: > On Thu, Jul 20, 2017 at 2:11 AM, Ingo Molnar wrote: >> Could you please also create a tabulated quick-comparison of the three >> variants, >> of all key properties, about behavior, feature and tradeoff

Re: [PATCH v6 0/2] x86: Implement fast refcount overflow protection

On Thu, Jul 20, 2017 at 10:15 AM, Kees Cook wrote: > On Thu, Jul 20, 2017 at 2:11 AM, Ingo Molnar wrote: >> Could you please also create a tabulated quick-comparison of the three >> variants, >> of all key properties, about behavior, feature and tradeoff differences? >> >> Something like: >> >>

[RFC PATCH 0/5] ima: namespacing IMA audit messages

This patch set implements an IMA namespace data structure that gets created alongside a mount namespace with CLONE_NEWNS, and lays down the foundation for namespacing the different aspects of IMA (eg. IMA-audit, IMA-measurement, IMA-appraisal). The original PoC patches [1], created a new

[RFC PATCH 0/5] ima: namespacing IMA audit messages

This patch set implements an IMA namespace data structure that gets created alongside a mount namespace with CLONE_NEWNS, and lays down the foundation for namespacing the different aspects of IMA (eg. IMA-audit, IMA-measurement, IMA-appraisal). The original PoC patches [1], created a new

Re: [PATCH] documentation: Fix two-CPU control-dependency example

On 2017/07/20 14:42:34 -0700, Paul E. McKenney wrote: > On Fri, Jul 21, 2017 at 06:12:56AM +0900, Akira Yokosawa wrote: >> On 2017/07/20 09:11:52AM -0700, Paul E. McKenney wrote: >>> On Thu, Jul 20, 2017 at 09:55:31PM +0900, Akira Yokosawa wrote: On 2017/07/20 14:47, Paul E. McKenney wrote:

Re: [PATCH] documentation: Fix two-CPU control-dependency example

On 2017/07/20 14:42:34 -0700, Paul E. McKenney wrote: > On Fri, Jul 21, 2017 at 06:12:56AM +0900, Akira Yokosawa wrote: >> On 2017/07/20 09:11:52AM -0700, Paul E. McKenney wrote: >>> On Thu, Jul 20, 2017 at 09:55:31PM +0900, Akira Yokosawa wrote: On 2017/07/20 14:47, Paul E. McKenney wrote:

Re: [PATCH RESEND v4] MAINTAINERS: fix lots of alphabetic ordering

On Thu, 2017-07-20 at 11:03 -0700, Linus Torvalds wrote: > On Thu, Jul 20, 2017 at 9:48 AM, Joe Perches wrote: > > > > Same general concept, but then an expectation would be > > relative paths for filename patterns. > > No, I actually think we really should require the

Re: [PATCH RESEND v4] MAINTAINERS: fix lots of alphabetic ordering

On Thu, 2017-07-20 at 11:03 -0700, Linus Torvalds wrote: > On Thu, Jul 20, 2017 at 9:48 AM, Joe Perches wrote: > > > > Same general concept, but then an expectation would be > > relative paths for filename patterns. > > No, I actually think we really should require the filename patterns to > be

Re: [PATCH] net: ethernet: ti: cpsw: Push the request_irq function to the end of probe

On 07/20/2017 05:28 PM, David Miller wrote: > From: Grygorii Strashko > Date: Thu, 20 Jul 2017 11:08:09 -0500 > >> In general patch looks good to me, but it's really unexpected to >> receive IRQs while CPSW is probing ;( > > This is a poor expectation. > > Boot

Re: [PATCH] net: ethernet: ti: cpsw: Push the request_irq function to the end of probe

On 07/20/2017 05:28 PM, David Miller wrote: > From: Grygorii Strashko > Date: Thu, 20 Jul 2017 11:08:09 -0500 > >> In general patch looks good to me, but it's really unexpected to >> receive IRQs while CPSW is probing ;( > > This is a poor expectation. > > Boot loaders and other entities can

Re: Modern Suspend on Dell Latitude 5285 does not resume

Good evening Mario, > Currently the patch does not look at anything in the system to default to S2I > vs S3. > This will affect systems that offer S3 and S2I (even if S3 is broken). > > Have you configured /sys/power/mem_sleep to s2idle? >

Re: Modern Suspend on Dell Latitude 5285 does not resume

Good evening Mario, > Currently the patch does not look at anything in the system to default to S2I > vs S3. > This will affect systems that offer S3 and S2I (even if S3 is broken). > > Have you configured /sys/power/mem_sleep to s2idle? >

Re: [PATCH] net: bonding: Fix transmit load balancing in balance-alb mode

From: Kosuke Tatsukawa Date: Thu, 20 Jul 2017 05:20:40 + > balance-alb mode used to have transmit dynamic load balancing feature > enabled by default. However, transmit dynamic load balancing no longer > works in balance-alb after commit 8b426dc54cf4 ("bonding: remove >

Re: [PATCH] net: bonding: Fix transmit load balancing in balance-alb mode

From: Kosuke Tatsukawa Date: Thu, 20 Jul 2017 05:20:40 + > balance-alb mode used to have transmit dynamic load balancing feature > enabled by default. However, transmit dynamic load balancing no longer > works in balance-alb after commit 8b426dc54cf4 ("bonding: remove > hardcoded value"). >

Re: [PATCH] lib/int_sqrt.c: Optimize square root function

On Thu, Jul 20, 2017 at 11:31:36AM -0700, Linus Torvalds wrote: > How did this two-year old thread get resurrected? I was looking for the original thread doing that 'optimization' Davidlohr did but found this first. > And the *most* important question is that first one: > > "Why does this

Re: [PATCH] lib/int_sqrt.c: Optimize square root function

On Thu, Jul 20, 2017 at 11:31:36AM -0700, Linus Torvalds wrote: > How did this two-year old thread get resurrected? I was looking for the original thread doing that 'optimization' Davidlohr did but found this first. > And the *most* important question is that first one: > > "Why does this

Re: [PATCH] Make functions rf69_set_bandwidth_intern and rf69_set_dc_cut_off_frequency_intern static

Oops, should have been marked as [V2] in the subject line On 20/07/17 23:33, Colin King wrote: > From: Colin Ian King > > The functions rf69_set_bandwidth_intern and also > rf69_set_dc_cut_off_frequency_intern is local to the source and > do not need to be in global

Re: [PATCH] Make functions rf69_set_bandwidth_intern and rf69_set_dc_cut_off_frequency_intern static

Oops, should have been marked as [V2] in the subject line On 20/07/17 23:33, Colin King wrote: > From: Colin Ian King > > The functions rf69_set_bandwidth_intern and also > rf69_set_dc_cut_off_frequency_intern is local to the source and > do not need to be in global scope, so make it static.

[PATCH] Make functions rf69_set_bandwidth_intern and rf69_set_dc_cut_off_frequency_intern static

From: Colin Ian King The functions rf69_set_bandwidth_intern and also rf69_set_dc_cut_off_frequency_intern is local to the source and do not need to be in global scope, so make it static. Also break break overly wide line. Finally, remove the function declaration

[PATCH] Make functions rf69_set_bandwidth_intern and rf69_set_dc_cut_off_frequency_intern static

From: Colin Ian King The functions rf69_set_bandwidth_intern and also rf69_set_dc_cut_off_frequency_intern is local to the source and do not need to be in global scope, so make it static. Also break break overly wide line. Finally, remove the function declaration

Re: [PATCH v3] sched/cputime: Fix using smp_processor_id() in preemptible

On Wed, Jul 19, 2017 at 4:38 PM, Paul McKenney wrote: > On Thu, Jul 13, 2017 at 11:49 PM, Wanpeng Li wrote: >> >> Ping for the merge window. :) >> 2017-07-09 15:40 GMT+08:00 Wanpeng Li : >> > From: Wanpeng Li

Re: [PATCH v3] sched/cputime: Fix using smp_processor_id() in preemptible

On Wed, Jul 19, 2017 at 4:38 PM, Paul McKenney wrote: > On Thu, Jul 13, 2017 at 11:49 PM, Wanpeng Li wrote: >> >> Ping for the merge window. :) >> 2017-07-09 15:40 GMT+08:00 Wanpeng Li : >> > From: Wanpeng Li >> > >> > BUG: using smp_processor_id() in preemptible [] code: >> >

Re: [PATCH net] rds: Make sure updates to cp_send_gen can be observed

From: Håkon Bugge Date: Thu, 20 Jul 2017 12:28:55 +0200 > cp->cp_send_gen is treated as a normal variable, although it may be > used by different threads. > > This is fixed by using {READ,WRITE}_ONCE when it is incremented and > READ_ONCE when it is read outside the

Re: [PATCH net] rds: Make sure updates to cp_send_gen can be observed

From: Håkon Bugge Date: Thu, 20 Jul 2017 12:28:55 +0200 > cp->cp_send_gen is treated as a normal variable, although it may be > used by different threads. > > This is fixed by using {READ,WRITE}_ONCE when it is incremented and > READ_ONCE when it is read outside the {acquire,release}_in_xmit >

Re: [PATCH] net: ethernet: ti: cpsw: Push the request_irq function to the end of probe

From: Grygorii Strashko Date: Thu, 20 Jul 2017 11:08:09 -0500 > In general patch looks good to me, but it's really unexpected to > receive IRQs while CPSW is probing ;( This is a poor expectation. Boot loaders and other entities can leave the device in any state

Re: [PATCH] net: ethernet: ti: cpsw: Push the request_irq function to the end of probe

From: Grygorii Strashko Date: Thu, 20 Jul 2017 11:08:09 -0500 > In general patch looks good to me, but it's really unexpected to > receive IRQs while CPSW is probing ;( This is a poor expectation. Boot loaders and other entities can leave the device in any state whatsoever. Furthermore,

Re: [PATCH V2] pci: quirk: Apply APM ACS quirk to XGene devices

On Wed, 19 Jul 2017 17:46:51 -0700 Feng Kan wrote: > The APM X-Gene PCIe root port does not support ACS at this point. > However, the hw provides isolation and source validation through > the SMMU. Turn on ACS but disable all the peer to peer features. > > Signed-off-by: Feng Kan

Re: [PATCH V2] pci: quirk: Apply APM ACS quirk to XGene devices

On Wed, 19 Jul 2017 17:46:51 -0700 Feng Kan wrote: > The APM X-Gene PCIe root port does not support ACS at this point. > However, the hw provides isolation and source validation through > the SMMU. Turn on ACS but disable all the peer to peer features. > > Signed-off-by: Feng Kan > --- >

Re: [PATCH net] net: dsa: b53: Add missing ARL entries for BCM53125

From: Florian Fainelli Date: Thu, 20 Jul 2017 12:25:22 -0700 > The BCM53125 entry was missing an arl_entries member which would > basically prevent the ARL search from terminating properly. This switch > has 4 ARL entries, so add that. > > Fixes: 1da6df85c6fb ("net: dsa:

Re: [PATCH net] net: dsa: b53: Add missing ARL entries for BCM53125

From: Florian Fainelli Date: Thu, 20 Jul 2017 12:25:22 -0700 > The BCM53125 entry was missing an arl_entries member which would > basically prevent the ARL search from terminating properly. This switch > has 4 ARL entries, so add that. > > Fixes: 1da6df85c6fb ("net: dsa: b53: Implement ARL

Re: [lkp-robot] [include/linux/string.h] 6974f0c455: kernel_BUG_at_lib/string.c

On Thu, 20 Jul 2017 11:41:38 -0700 Linus Torvalds wrote: > On Thu, Jul 20, 2017 at 8:51 AM, Masami Hiramatsu wrote: > > > > Acked-by: Masami Hiramatsu > > Tested-by: Masami Hiramatsu > > Ok, I

Re: [lkp-robot] [include/linux/string.h] 6974f0c455: kernel_BUG_at_lib/string.c

On Thu, 20 Jul 2017 11:41:38 -0700 Linus Torvalds wrote: > On Thu, Jul 20, 2017 at 8:51 AM, Masami Hiramatsu wrote: > > > > Acked-by: Masami Hiramatsu > > Tested-by: Masami Hiramatsu > > Ok, I committed that patch as-is. > > Other architectures may end up with the same issue, unless they

Re: [PATCH] pci: quirk: Apply APM ACS quirk to XGene devices

On Tue, 18 Jul 2017 22:37:00 -0700 Feng Kan wrote: > > > > I don't know what that means, does the hardware support an equivalent > > to source validation or not? > > Yes, source validation is done through the smmu. The SMMU does a context lookup based on the bdf, but if the

Re: [PATCH] pci: quirk: Apply APM ACS quirk to XGene devices

On Tue, 18 Jul 2017 22:37:00 -0700 Feng Kan wrote: > > > > I don't know what that means, does the hardware support an equivalent > > to source validation or not? > > Yes, source validation is done through the smmu. The SMMU does a context lookup based on the bdf, but if the root port does

Re: [RFC v6 27/62] powerpc: helper to validate key-access permissions of a pte

On Thu, Jul 20, 2017 at 12:12:47PM +0530, Aneesh Kumar K.V wrote: > Ram Pai writes: > > > helper function that checks if the read/write/execute is allowed > > on the pte. > > > > Signed-off-by: Ram Pai > > --- > >

Re: [RFC v6 27/62] powerpc: helper to validate key-access permissions of a pte

On Thu, Jul 20, 2017 at 12:12:47PM +0530, Aneesh Kumar K.V wrote: > Ram Pai writes: > > > helper function that checks if the read/write/execute is allowed > > on the pte. > > > > Signed-off-by: Ram Pai > > --- > > arch/powerpc/include/asm/book3s/64/pgtable.h |4 +++ > >

[PATCH][V2] dvb_frontend: ensure that inital front end status initialized

From: Colin Ian King The fe_status variable s is not initialized meaning it can have any random garbage status. This could be problematic if fe->ops.tune is false as s is not updated by the call to fe->ops.tune() and a subsequent check on the change status will using a

[PATCH][V2] dvb_frontend: ensure that inital front end status initialized

From: Colin Ian King The fe_status variable s is not initialized meaning it can have any random garbage status. This could be problematic if fe->ops.tune is false as s is not updated by the call to fe->ops.tune() and a subsequent check on the change status will using a garbage value. Fix this

Re: [RFC v6 11/62] powerpc: initial pkey plumbing

On Thu, Jul 20, 2017 at 11:34:10AM +0530, Aneesh Kumar K.V wrote: > Ram Pai writes: > > > basic setup to initialize the pkey system. Only 64K kernel in HPT > > mode, enables the pkey system. > > > > Signed-off-by: Ram Pai > > --- > >

Re: [RFC v6 11/62] powerpc: initial pkey plumbing

On Thu, Jul 20, 2017 at 11:34:10AM +0530, Aneesh Kumar K.V wrote: > Ram Pai writes: > > > basic setup to initialize the pkey system. Only 64K kernel in HPT > > mode, enables the pkey system. > > > > Signed-off-by: Ram Pai > > --- > > arch/powerpc/Kconfig | 16 ++ > >

[PATCH v2] x86/platform/uv/BAU: disable BAU on single hub configurations

The BAU confers no benefit to a UV system running with only one hub/socket. Permanently disable the BAU driver if there are less than two hubs online to avoid BAU overhead. We have observed failed boots on single-socket UV4 systems caused by BAU that are avoided with this patch. Version 2:

[PATCH v2] x86/platform/uv/BAU: disable BAU on single hub configurations

The BAU confers no benefit to a UV system running with only one hub/socket. Permanently disable the BAU driver if there are less than two hubs online to avoid BAU overhead. We have observed failed boots on single-socket UV4 systems caused by BAU that are avoided with this patch. Version 2:

Re: [Nouveau] [PATCH] drm: disable vblank only if it got previously enabled

On Thu, Jul 20, 2017 at 11:58 PM, Tobias Klausmann wrote: > Mh ok, > > paper over in nouveau_display_fini until Ben comes up with a better idea > then?! No paper needed, just don't call drm_vblank_off for the atomic case. Not sure why that patch isn't landed

Re: [Nouveau] [PATCH] drm: disable vblank only if it got previously enabled

On Thu, Jul 20, 2017 at 11:58 PM, Tobias Klausmann wrote: > Mh ok, > > paper over in nouveau_display_fini until Ben comes up with a better idea > then?! No paper needed, just don't call drm_vblank_off for the atomic case. Not sure why that patch isn't landed yet, it should be simple. -Daniel >

Re: [RFC v6 01/62] powerpc: Free up four 64K PTE bits in 4K backed HPTE pages

On Thu, Jul 20, 2017 at 11:21:51AM +0530, Aneesh Kumar K.V wrote: > > . > > > /* > > @@ -116,8 +104,8 @@ int __hash_page_4K(unsigned long ea, unsigned long > > access, unsigned long vsid, > > * On hash insert failure we use old pte value and we don't > > * want

Re: [RFC v6 01/62] powerpc: Free up four 64K PTE bits in 4K backed HPTE pages

On Thu, Jul 20, 2017 at 11:21:51AM +0530, Aneesh Kumar K.V wrote: > > . > > > /* > > @@ -116,8 +104,8 @@ int __hash_page_4K(unsigned long ea, unsigned long > > access, unsigned long vsid, > > * On hash insert failure we use old pte value and we don't > > * want

Re: [PATCH] ACPI / PM / EC: Flush all EC work in acpi_freeze_sync()

On Thursday, July 20, 2017 03:43:12 AM Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > Commit eed4d47efe95 (ACPI / sleep: Ignore spurious SCI wakeups from > suspend-to-idle) introduced acpi_freeze_sync() whose purpose is to > flush all of the processing of

Re: [PATCH] ACPI / PM / EC: Flush all EC work in acpi_freeze_sync()

On Thursday, July 20, 2017 03:43:12 AM Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > Commit eed4d47efe95 (ACPI / sleep: Ignore spurious SCI wakeups from > suspend-to-idle) introduced acpi_freeze_sync() whose purpose is to > flush all of the processing of possible wakeup events signaled

Re: [PATCH 3/3] PM / timekeeping: Print debug messages when requested

On Wednesday, July 19, 2017 02:42:43 AM Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > The messages printed by tk_debug_account_sleep_time() are basically > useful for system sleep debugging, so print them only when the other > debug messages from the core

Re: [PATCH 3/3] PM / timekeeping: Print debug messages when requested

On Wednesday, July 19, 2017 02:42:43 AM Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > The messages printed by tk_debug_account_sleep_time() are basically > useful for system sleep debugging, so print them only when the other > debug messages from the core suspend/hibernate code are

Re: [Nouveau] [PATCH] drm: disable vblank only if it got previously enabled

Mh ok, paper over in nouveau_display_fini until Ben comes up with a better idea then?! Greetings, Tobias On 7/20/17 10:13 AM, Daniel Vetter wrote: > On Wed, Jul 19, 2017 at 04:10:50PM -0400, Ilia Mirkin wrote: >> I believe the solution is to not call drm_crtc_vblank_off for atomic >>

Re: [Nouveau] [PATCH] drm: disable vblank only if it got previously enabled

Mh ok, paper over in nouveau_display_fini until Ben comes up with a better idea then?! Greetings, Tobias On 7/20/17 10:13 AM, Daniel Vetter wrote: > On Wed, Jul 19, 2017 at 04:10:50PM -0400, Ilia Mirkin wrote: >> I believe the solution is to not call drm_crtc_vblank_off for atomic >>

[GIT PULL] Power management fixes for v4.13-rc2

Hi Linus, Please pull from the tag git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \ pm-4.13-rc2 with top-most commit ffa64d5e0d2f053d76ff9b1d2f437150b49c4112 Merge branches 'intel_pstate' and 'pm-domains' on top of commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877 Linux

[GIT PULL] Power management fixes for v4.13-rc2

Hi Linus, Please pull from the tag git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \ pm-4.13-rc2 with top-most commit ffa64d5e0d2f053d76ff9b1d2f437150b49c4112 Merge branches 'intel_pstate' and 'pm-domains' on top of commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877 Linux

Re: [PATCH] oom_reaper: close race without using oom_lock

Michal Hocko wrote: > On Wed 19-07-17 05:51:03, Tetsuo Handa wrote: > > Michal Hocko wrote: > > > On Tue 18-07-17 23:06:50, Tetsuo Handa wrote: > > > > Commit e2fe14564d3316d1 ("oom_reaper: close race with exiting task") > > > > guarded whole OOM reaping operations using oom_lock. But there was no

Re: [PATCH] oom_reaper: close race without using oom_lock

Michal Hocko wrote: > On Wed 19-07-17 05:51:03, Tetsuo Handa wrote: > > Michal Hocko wrote: > > > On Tue 18-07-17 23:06:50, Tetsuo Handa wrote: > > > > Commit e2fe14564d3316d1 ("oom_reaper: close race with exiting task") > > > > guarded whole OOM reaping operations using oom_lock. But there was no

<    1   2   3   4   5   6   7   8   9   10   >