linux-next: Tree for Feb 8

Hi all, Changes since 20170207: The kspp tree gained conflicts against Linus' and the arm-soc, net-next and s390 trees. The kvm tree gained a build failure so I used the version from next-20170207. The gpio tree gained a build failure from an interaction with the tty tree. I applied a merge

[PATCH 2/2] drivers: usb: gadget: udc: remove logically dead code

Remove unnecesary code because zlt never evaluates to zero. Addresses-Coverity-ID: 1226747 Signed-off-by: Gustavo A. R. Silva --- drivers/usb/gadget/udc/mv_udc_core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 2/2] drivers: usb: gadget: udc: remove logically dead code

Remove unnecesary code because zlt never evaluates to zero. Addresses-Coverity-ID: 1226747 Signed-off-by: Gustavo A. R. Silva --- drivers/usb/gadget/udc/mv_udc_core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/usb/gadget/udc/mv_udc_core.c

linux-next: Tree for Feb 8

Hi all, Changes since 20170207: The kspp tree gained conflicts against Linus' and the arm-soc, net-next and s390 trees. The kvm tree gained a build failure so I used the version from next-20170207. The gpio tree gained a build failure from an interaction with the tty tree. I applied a merge

Re: [PATCH v4] drivers/misc: Add Aspeed LPC control driver

On Wed, 2017-02-08 at 02:06 +0200, Andy Shevchenko wrote: > > On Wed, Feb 8, 2017 at 1:42 AM, Cyril Bur wrote: > > In order to manage server systems, there is typically another processor > > known as a BMC (Baseboard Management Controller) which is responsible > > for powering

Re: [PATCH v4] drivers/misc: Add Aspeed LPC control driver

On Wed, 2017-02-08 at 02:06 +0200, Andy Shevchenko wrote: > > On Wed, Feb 8, 2017 at 1:42 AM, Cyril Bur wrote: > > In order to manage server systems, there is typically another processor > > known as a BMC (Baseboard Management Controller) which is responsible > > for powering the server and

Re: [PATCH v2] staging: rtl8712: rtl8712: fix sparse warnings

On Wed, Feb 08, 2017 at 01:23:15AM +, Carlos Palminha wrote: > Fixed sparse warnings > * No need to convert from le32, pointers for structure with same endianness > (cast from restricted __le32) > * Need to convert bitwise operation for le32 structure (invalid assignment > from int to

Re: [PATCH v2] staging: rtl8712: rtl8712: fix sparse warnings

On Wed, Feb 08, 2017 at 01:23:15AM +, Carlos Palminha wrote: > Fixed sparse warnings > * No need to convert from le32, pointers for structure with same endianness > (cast from restricted __le32) > * Need to convert bitwise operation for le32 structure (invalid assignment > from int to

[GIT PULL][SECURITY] selinux: fix off-by-one in setprocattr

Please pull this fix for a bug in SELinux, which fixes CVE-2017-2618. The following changes since commit 926af6273fc683cd98cd0ce7bf0d04a02eed6742: Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2017-02-07 12:10:57 -0800) are available in the git repository at:

[GIT PULL][SECURITY] selinux: fix off-by-one in setprocattr

Please pull this fix for a bug in SELinux, which fixes CVE-2017-2618. The following changes since commit 926af6273fc683cd98cd0ce7bf0d04a02eed6742: Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2017-02-07 12:10:57 -0800) are available in the git repository at:

Re: mm: deadlock between get_online_cpus/pcpu_alloc

On Tue 07-02-17 23:25:17, Thomas Gleixner wrote: > On Tue, 7 Feb 2017, Christoph Lameter wrote: > > On Tue, 7 Feb 2017, Michal Hocko wrote: > > > > > I am always nervous when seeing hotplug locks being used in low level > > > code. It has bitten us several times already and those deadlocks are >

Re: mm: deadlock between get_online_cpus/pcpu_alloc

On Tue 07-02-17 23:25:17, Thomas Gleixner wrote: > On Tue, 7 Feb 2017, Christoph Lameter wrote: > > On Tue, 7 Feb 2017, Michal Hocko wrote: > > > > > I am always nervous when seeing hotplug locks being used in low level > > > code. It has bitten us several times already and those deadlocks are >

Re: [PATCH 1/2] drm/rockchip: support mode_valid for crtc

On Wed, Feb 8, 2017 at 1:45 AM, Mark yao wrote: > On 2017年02月08日 00:14, Sean Paul wrote: >> >> On Sun, Feb 05, 2017 at 03:36:36PM +0800, Mark Yao wrote: >>> >>> drm crtc already has mode_fixup callback to can do mode check, but >>> We actually want to valid display mode

Re: [PATCH 1/2] drm/rockchip: support mode_valid for crtc

On Wed, Feb 8, 2017 at 1:45 AM, Mark yao wrote: > On 2017年02月08日 00:14, Sean Paul wrote: >> >> On Sun, Feb 05, 2017 at 03:36:36PM +0800, Mark Yao wrote: >>> >>> drm crtc already has mode_fixup callback to can do mode check, but >>> We actually want to valid display mode on connector getmode time,

[PATCH 1/2 v2] cpufreq: qoriq: added arm64 socs support

From: Tang Yuantian Add arm64 config to Kconfig to enable cpu frequency feature on nxp arm64 socs. Signed-off-by: Tang Yuantian --- v2: - no change drivers/cpufreq/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 1/2 v2] cpufreq: qoriq: added arm64 socs support

From: Tang Yuantian Add arm64 config to Kconfig to enable cpu frequency feature on nxp arm64 socs. Signed-off-by: Tang Yuantian --- v2: - no change drivers/cpufreq/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/cpufreq/Kconfig b/drivers/cpufreq/Kconfig

Re: [RFC PATCH v4] IV Generation algorithms for dm-crypt

On Tue, Feb 7, 2017 at 12:35 PM, Binoy Jayan wrote: > === > dm-crypt optimization for larger block sizes > === > >

[PATCH 2/2 v2] cpufreq: qoriq: Don't look at clock implementation details

From: Tang Yuantian Get the CPU clock's potential parent clocks from the clock interface itself, rather than manually parsing the clocks property to find a phandle, looking at the clock-names property of that, and assuming that those are valid parent clocks for the cpu

Re: [RFC PATCH v4] IV Generation algorithms for dm-crypt

On Tue, Feb 7, 2017 at 12:35 PM, Binoy Jayan wrote: > === > dm-crypt optimization for larger block sizes > === > > Currently, the iv generation

[PATCH 2/2 v2] cpufreq: qoriq: Don't look at clock implementation details

From: Tang Yuantian Get the CPU clock's potential parent clocks from the clock interface itself, rather than manually parsing the clocks property to find a phandle, looking at the clock-names property of that, and assuming that those are valid parent clocks for the cpu clock. This is necessary

Re: [RFC][PATCH] treewide: Move set_memory_* functions away from cacheflush.h

* Laura Abbott wrote: > The set_memory_* APIs came out of a desire to have a better way to > change memory attributes. Many of these attributes were linked to cache > functionality so the prototypes were put in cacheflush.h. These days, > the APIs have grown and have a much

Re: [RFC][PATCH] treewide: Move set_memory_* functions away from cacheflush.h

* Laura Abbott wrote: > The set_memory_* APIs came out of a desire to have a better way to > change memory attributes. Many of these attributes were linked to cache > functionality so the prototypes were put in cacheflush.h. These days, > the APIs have grown and have a much wider use than just

[tip:locking/urgent] stacktrace, lockdep: Fix address, newline ugliness

Commit-ID: bfeda41d06d85ad9d52f2413cfc2b77be5022f75 Gitweb: http://git.kernel.org/tip/bfeda41d06d85ad9d52f2413cfc2b77be5022f75 Author: Omar Sandoval AuthorDate: Tue, 7 Feb 2017 15:33:20 -0800 Committer: Ingo Molnar CommitDate: Wed, 8 Feb 2017 08:21:31

[tip:locking/urgent] stacktrace, lockdep: Fix address, newline ugliness

Commit-ID: bfeda41d06d85ad9d52f2413cfc2b77be5022f75 Gitweb: http://git.kernel.org/tip/bfeda41d06d85ad9d52f2413cfc2b77be5022f75 Author: Omar Sandoval AuthorDate: Tue, 7 Feb 2017 15:33:20 -0800 Committer: Ingo Molnar CommitDate: Wed, 8 Feb 2017 08:21:31 +0100 stacktrace, lockdep: Fix

Re: [PATCH v2] drm/mxsfb: fix pixel clock polarity

On Wed, Feb 8, 2017 at 6:19 AM, Stefan Agner wrote: > On 2016-12-14 13:25, Marek Vasut wrote: >> On 12/14/2016 09:48 PM, Stefan Agner wrote: >>> The DRM subsystem specifies the pixel clock polarity from a >>> controllers perspective: DRM_BUS_FLAG_PIXDATA_NEGEDGE means >>> the

Re: [PATCH v2] drm/mxsfb: fix pixel clock polarity

On Wed, Feb 8, 2017 at 6:19 AM, Stefan Agner wrote: > On 2016-12-14 13:25, Marek Vasut wrote: >> On 12/14/2016 09:48 PM, Stefan Agner wrote: >>> The DRM subsystem specifies the pixel clock polarity from a >>> controllers perspective: DRM_BUS_FLAG_PIXDATA_NEGEDGE means >>> the controller drives

Re: [PATCH v2] locking/pvqspinlock: Relax cmpxchg's to improve performance on some archs

On Wed, Feb 08, 2017 at 03:09:33PM +0800, Pan Xinhui wrote: > > > 在 2017/2/8 14:09, Boqun Feng 写道: > > On Wed, Feb 08, 2017 at 12:05:40PM +0800, Boqun Feng wrote: > > > On Wed, Feb 08, 2017 at 11:39:10AM +0800, Xinhui Pan wrote: > > > > 2016-12-26 4:26 GMT+08:00 Waiman Long :

Re: [PATCH v2] locking/pvqspinlock: Relax cmpxchg's to improve performance on some archs

On Wed, Feb 08, 2017 at 03:09:33PM +0800, Pan Xinhui wrote: > > > 在 2017/2/8 14:09, Boqun Feng 写道: > > On Wed, Feb 08, 2017 at 12:05:40PM +0800, Boqun Feng wrote: > > > On Wed, Feb 08, 2017 at 11:39:10AM +0800, Xinhui Pan wrote: > > > > 2016-12-26 4:26 GMT+08:00 Waiman Long : > > > > > > > > >

Re: [PATCH v2] locking/pvqspinlock: Relax cmpxchg's to improve performance on some archs

在 2017/2/8 14:09, Boqun Feng 写道: On Wed, Feb 08, 2017 at 12:05:40PM +0800, Boqun Feng wrote: On Wed, Feb 08, 2017 at 11:39:10AM +0800, Xinhui Pan wrote: 2016-12-26 4:26 GMT+08:00 Waiman Long : A number of cmpxchg calls in qspinlock_paravirt.h were replaced by more

Re: [PATCH v2] locking/pvqspinlock: Relax cmpxchg's to improve performance on some archs

在 2017/2/8 14:09, Boqun Feng 写道: On Wed, Feb 08, 2017 at 12:05:40PM +0800, Boqun Feng wrote: On Wed, Feb 08, 2017 at 11:39:10AM +0800, Xinhui Pan wrote: 2016-12-26 4:26 GMT+08:00 Waiman Long : A number of cmpxchg calls in qspinlock_paravirt.h were replaced by more relaxed versions to

Re: [PATCH 4/7] serial: exar: Move Commtech adapters to 8250_exar as well

On 2017-02-08 00:23, Andy Shevchenko wrote: > On Tue, Feb 7, 2017 at 6:10 PM, Jan Kiszka wrote: >> Those are exar-based, too. > > Exar-based > >> With the required refactoring of the code to fit into 8250_exar, we >> automatically fix the same issue pci_xr17v35x_setup

Re: [PATCH 4/7] serial: exar: Move Commtech adapters to 8250_exar as well

On 2017-02-08 00:23, Andy Shevchenko wrote: > On Tue, Feb 7, 2017 at 6:10 PM, Jan Kiszka wrote: >> Those are exar-based, too. > > Exar-based > >> With the required refactoring of the code to fit into 8250_exar, we >> automatically fix the same issue pci_xr17v35x_setup had before: 8XMODE, >>

Re: v4.9, 4.4-final: 28 bioset threads on small notebook, 36 threads on cellphone

On Tue, 2017-02-07 at 19:58 -0900, Kent Overstreet wrote: > On Tue, Feb 07, 2017 at 09:39:11PM +0100, Pavel Machek wrote: > > On Mon 2017-02-06 17:49:06, Kent Overstreet wrote: > > > On Mon, Feb 06, 2017 at 04:47:24PM -0900, Kent Overstreet wrote: > > > > On Mon, Feb 06, 2017 at 01:53:09PM +0100,

Re: v4.9, 4.4-final: 28 bioset threads on small notebook, 36 threads on cellphone

On Tue, 2017-02-07 at 19:58 -0900, Kent Overstreet wrote: > On Tue, Feb 07, 2017 at 09:39:11PM +0100, Pavel Machek wrote: > > On Mon 2017-02-06 17:49:06, Kent Overstreet wrote: > > > On Mon, Feb 06, 2017 at 04:47:24PM -0900, Kent Overstreet wrote: > > > > On Mon, Feb 06, 2017 at 01:53:09PM +0100,

Re: [PATCH 3.10 141/319] scsi: mpt3sas: Fix secure erase premature termination

On Tue, Feb 07, 2017 at 06:12:34PM +0100, Willy Tarreau wrote: > On Tue, Feb 07, 2017 at 09:02:51AM -0800, James Bottomley wrote: > > On Tue, 2017-02-07 at 07:59 +0100, Willy Tarreau wrote: > > > Hi James, > > > > > > On Mon, Feb 06, 2017 at 10:38:48PM -0800, James Bottomley wrote: > > > > On

Re: [PATCH 3.10 141/319] scsi: mpt3sas: Fix secure erase premature termination

On Tue, Feb 07, 2017 at 06:12:34PM +0100, Willy Tarreau wrote: > On Tue, Feb 07, 2017 at 09:02:51AM -0800, James Bottomley wrote: > > On Tue, 2017-02-07 at 07:59 +0100, Willy Tarreau wrote: > > > Hi James, > > > > > > On Mon, Feb 06, 2017 at 10:38:48PM -0800, James Bottomley wrote: > > > > On

Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount

On Wed, Feb 8, 2017 at 1:42 AM, James Bottomley wrote: > On Tue, 2017-02-07 at 14:25 -0800, Christoph Hellwig wrote: >> On Tue, Feb 07, 2017 at 11:01:29PM +0200, Amir Goldstein wrote: >> > Project id's are not exactly "subtree" semantic, but inheritance >> >

Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount

On Wed, Feb 8, 2017 at 1:42 AM, James Bottomley wrote: > On Tue, 2017-02-07 at 14:25 -0800, Christoph Hellwig wrote: >> On Tue, Feb 07, 2017 at 11:01:29PM +0200, Amir Goldstein wrote: >> > Project id's are not exactly "subtree" semantic, but inheritance >> > semantics, >> > which is not the same

Re: [PATCH v2] locking/pvqspinlock: Relax cmpxchg's to improve performance on some archs

在 2017/2/8 14:09, Boqun Feng 写道: On Wed, Feb 08, 2017 at 12:05:40PM +0800, Boqun Feng wrote: On Wed, Feb 08, 2017 at 11:39:10AM +0800, Xinhui Pan wrote: 2016-12-26 4:26 GMT+08:00 Waiman Long : A number of cmpxchg calls in qspinlock_paravirt.h were replaced by more

Re: [PATCH v2] locking/pvqspinlock: Relax cmpxchg's to improve performance on some archs

在 2017/2/8 14:09, Boqun Feng 写道: On Wed, Feb 08, 2017 at 12:05:40PM +0800, Boqun Feng wrote: On Wed, Feb 08, 2017 at 11:39:10AM +0800, Xinhui Pan wrote: 2016-12-26 4:26 GMT+08:00 Waiman Long : A number of cmpxchg calls in qspinlock_paravirt.h were replaced by more relaxed versions to

Re: [PATCH v2] locking/pvqspinlock: Relax cmpxchg's to improve performance on some archs

在 2017/2/8 14:09, Boqun Feng 写道: On Wed, Feb 08, 2017 at 12:05:40PM +0800, Boqun Feng wrote: On Wed, Feb 08, 2017 at 11:39:10AM +0800, Xinhui Pan wrote: 2016-12-26 4:26 GMT+08:00 Waiman Long : A number of cmpxchg calls in qspinlock_paravirt.h were replaced by more

Re: [PATCH v2] locking/pvqspinlock: Relax cmpxchg's to improve performance on some archs

在 2017/2/8 14:09, Boqun Feng 写道: On Wed, Feb 08, 2017 at 12:05:40PM +0800, Boqun Feng wrote: On Wed, Feb 08, 2017 at 11:39:10AM +0800, Xinhui Pan wrote: 2016-12-26 4:26 GMT+08:00 Waiman Long : A number of cmpxchg calls in qspinlock_paravirt.h were replaced by more relaxed versions to

[PATCH] drivers: usb: early: remove unused code

Remove this line of code because devnum is overwritten before it can be used. This could happen if line of code 609 (goto try_again;) is executed. Otherwise, devnum is never used again. Addresses-Coverity-ID: 1226870 Signed-off-by: Gustavo A. R. Silva ---

[PATCH] drivers: usb: early: remove unused code

Remove this line of code because devnum is overwritten before it can be used. This could happen if line of code 609 (goto try_again;) is executed. Otherwise, devnum is never used again. Addresses-Coverity-ID: 1226870 Signed-off-by: Gustavo A. R. Silva --- drivers/usb/early/ehci-dbgp.c | 1 - 1

Re: [PATCH v2 2/5] async_tx: Handle DMA devices having support for fewer PQ coefficients

On Tue, Feb 7, 2017 at 10:12 PM, Vinod Koul wrote: > On Tue, Feb 07, 2017 at 02:32:15PM +0530, Anup Patel wrote: >> On Tue, Feb 7, 2017 at 1:57 PM, Dan Williams >> wrote: >> > On Tue, Feb 7, 2017 at 12:16 AM, Anup Patel

Re: [PATCH v2 2/5] async_tx: Handle DMA devices having support for fewer PQ coefficients

On Tue, Feb 7, 2017 at 10:12 PM, Vinod Koul wrote: > On Tue, Feb 07, 2017 at 02:32:15PM +0530, Anup Patel wrote: >> On Tue, Feb 7, 2017 at 1:57 PM, Dan Williams >> wrote: >> > On Tue, Feb 7, 2017 at 12:16 AM, Anup Patel >> > wrote: >> >> The DMAENGINE framework assumes that if PQ offload is

Re: [PATCH 4.9 00/66] 4.9.9-stable review

On Tue, Feb 07, 2017 at 04:27:32PM -0800, kernelci.org bot wrote: > stable-rc boot: 217 boots: 0 failed, 207 passed with 10 offline > (v4.9.8-67-gf1cb727f439b) 0 failed! Wow, either you all fixed the build system, or something went right here :) thanks for the report. greg k-h

Re: [PATCH 4.9 00/66] 4.9.9-stable review

On Tue, Feb 07, 2017 at 04:27:32PM -0800, kernelci.org bot wrote: > stable-rc boot: 217 boots: 0 failed, 207 passed with 10 offline > (v4.9.8-67-gf1cb727f439b) 0 failed! Wow, either you all fixed the build system, or something went right here :) thanks for the report. greg k-h

Re: [PATCH 4.9 00/66] 4.9.9-stable review

On Tue, Feb 07, 2017 at 01:44:41PM -0800, Guenter Roeck wrote: > On Tue, Feb 07, 2017 at 01:58:34PM +0100, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.9.9 release. > > There are 66 patches in this series, all will be posted as a response > > to this one.

Re: [PATCH 4.9 00/66] 4.9.9-stable review

On Tue, Feb 07, 2017 at 01:44:41PM -0800, Guenter Roeck wrote: > On Tue, Feb 07, 2017 at 01:58:34PM +0100, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.9.9 release. > > There are 66 patches in this series, all will be posted as a response > > to this one.

Re: [PATCH 4.4 00/29] 4.4.48-stable review

On Tue, Feb 07, 2017 at 05:27:32PM -0800, kernelci.org bot wrote: > stable-rc boot: 517 boots: 0 failed, 498 passed with 19 offline > (v4.4.47-30-gcd13c41318b2) Why is there almost double the number of "passed" systems here compared to 4.9? thanks, greg k-h

Re: [PATCH 4.4 00/29] 4.4.48-stable review

On Tue, Feb 07, 2017 at 05:27:32PM -0800, kernelci.org bot wrote: > stable-rc boot: 517 boots: 0 failed, 498 passed with 19 offline > (v4.4.47-30-gcd13c41318b2) Why is there almost double the number of "passed" systems here compared to 4.9? thanks, greg k-h

Re: [lustre-devel] [PATCH 10/60] staging: lustre: obdclass: add more info to sysfs version string

On Wed, Feb 08, 2017 at 01:04:52AM +, Dilger, Andreas wrote: > > > On Feb 3, 2017, at 03:33, Greg Kroah-Hartman > > wrote: > > > > On Sat, Jan 28, 2017 at 07:04:38PM -0500, James Simmons wrote: > >> From: Andreas Dilger > >> > >>

Re: [lustre-devel] [PATCH 10/60] staging: lustre: obdclass: add more info to sysfs version string

On Wed, Feb 08, 2017 at 01:04:52AM +, Dilger, Andreas wrote: > > > On Feb 3, 2017, at 03:33, Greg Kroah-Hartman > > wrote: > > > > On Sat, Jan 28, 2017 at 07:04:38PM -0500, James Simmons wrote: > >> From: Andreas Dilger > >> > >> Update the sysfs "version" file to print "lustre: " with >

Re: [PATCH] block: Make rescuer threads per request_queue, not per bioset

Hi Kent, [auto build test WARNING on linus/master] [also build test WARNING on v4.10-rc7] [cannot apply to next-20170207] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Kent-Overstreet/block

Re: [PATCH] block: Make rescuer threads per request_queue, not per bioset

Hi Kent, [auto build test ERROR on linus/master] [also build test ERROR on v4.10-rc7] [cannot apply to next-20170207] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Kent-Overstreet/block-Make

Re: [PATCH] block: Make rescuer threads per request_queue, not per bioset

Hi Kent, [auto build test WARNING on linus/master] [also build test WARNING on v4.10-rc7] [cannot apply to next-20170207] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Kent-Overstreet/block

Re: [PATCH] block: Make rescuer threads per request_queue, not per bioset

Hi Kent, [auto build test ERROR on linus/master] [also build test ERROR on v4.10-rc7] [cannot apply to next-20170207] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Kent-Overstreet/block-Make

Re: [PATCH v3 3/3] xen: optimize xenbus driver for multiple concurrent xenstore accesses

On 07/02/17 23:39, Boris Ostrovsky wrote: > On 02/07/2017 12:51 PM, Boris Ostrovsky wrote: >> On 01/24/2017 11:23 AM, Juergen Gross wrote: >>> On 24/01/17 14:47, Boris Ostrovsky wrote: On 01/23/2017 01:59 PM, Boris Ostrovsky wrote: > On 01/23/2017 05:09 AM, Juergen Gross wrote: >>

Re: [PATCH v3 3/3] xen: optimize xenbus driver for multiple concurrent xenstore accesses

On 07/02/17 23:39, Boris Ostrovsky wrote: > On 02/07/2017 12:51 PM, Boris Ostrovsky wrote: >> On 01/24/2017 11:23 AM, Juergen Gross wrote: >>> On 24/01/17 14:47, Boris Ostrovsky wrote: On 01/23/2017 01:59 PM, Boris Ostrovsky wrote: > On 01/23/2017 05:09 AM, Juergen Gross wrote: >>

[PATCH 1/2] spi: imx: dynamic burst length adjust for PIO mode

previously burst length (BURST_LENGTH) is always set to equal to bits_per_word, causes a 10us gap between each word in transfer, which significantly affects performance. This patch uses 32 bits transfer to simulate lower bits transfer, and adjusts burst length runtimely to use biggeest burst

[PATCH 1/2] spi: imx: dynamic burst length adjust for PIO mode

previously burst length (BURST_LENGTH) is always set to equal to bits_per_word, causes a 10us gap between each word in transfer, which significantly affects performance. This patch uses 32 bits transfer to simulate lower bits transfer, and adjusts burst length runtimely to use biggeest burst

[PATCH 2/2] spi: imx: dynamic burst length adjust for DMA mode

previously burst length (BURST_LENGTH) is always set to equal to bits_per_word, causes a 10us gap between each word in transfer, which significantly affects performance. This patch uses 32 bits transfer to simulate lower bits transfer, and adjusts burst length to reduce the number of gaps in DMA

[PATCH linux-next v1 0/2] improve imx spi performance

previously burst length (BURST_LENGTH) is always set to equal to bits_per_word, causes a 10us gap between each word in transfer, which significantly affects performance. This patch set uses 32 bits tranfser to simulate lowers bits transfer, and by set burst length to maximum possible value to

[PATCH linux-next v1 0/2] improve imx spi performance

previously burst length (BURST_LENGTH) is always set to equal to bits_per_word, causes a 10us gap between each word in transfer, which significantly affects performance. This patch set uses 32 bits tranfser to simulate lowers bits transfer, and by set burst length to maximum possible value to

[PATCH 2/2] spi: imx: dynamic burst length adjust for DMA mode

previously burst length (BURST_LENGTH) is always set to equal to bits_per_word, causes a 10us gap between each word in transfer, which significantly affects performance. This patch uses 32 bits transfer to simulate lower bits transfer, and adjusts burst length to reduce the number of gaps in DMA

Re: [PATCH] staging: rtl8712: rtl8712: fix sparse warnings

On Wed, Feb 08, 2017 at 01:19:39AM +, Carlos Palminha wrote: > > > On 08-02-2017 00:58, Dan Carpenter wrote: > >On Wed, Feb 08, 2017 at 12:47:22AM +, Carlos Palminha wrote: > >>Fixed the following sparse warnings: > >>* cast from restricted __le32 > >>* invalid assignment from int to

Re: [PATCH] staging: rtl8712: rtl8712: fix sparse warnings

On Wed, Feb 08, 2017 at 01:19:39AM +, Carlos Palminha wrote: > > > On 08-02-2017 00:58, Dan Carpenter wrote: > >On Wed, Feb 08, 2017 at 12:47:22AM +, Carlos Palminha wrote: > >>Fixed the following sparse warnings: > >>* cast from restricted __le32 > >>* invalid assignment from int to

Re: [PATCH v2] locking/pvqspinlock: Relax cmpxchg's to improve performance on some archs

On Wed, Feb 08, 2017 at 12:05:40PM +0800, Boqun Feng wrote: > On Wed, Feb 08, 2017 at 11:39:10AM +0800, Xinhui Pan wrote: > > 2016-12-26 4:26 GMT+08:00 Waiman Long : > > > > > A number of cmpxchg calls in qspinlock_paravirt.h were replaced by more > > > relaxed versions to

Re: [PATCH v2] locking/pvqspinlock: Relax cmpxchg's to improve performance on some archs

On Wed, Feb 08, 2017 at 12:05:40PM +0800, Boqun Feng wrote: > On Wed, Feb 08, 2017 at 11:39:10AM +0800, Xinhui Pan wrote: > > 2016-12-26 4:26 GMT+08:00 Waiman Long : > > > > > A number of cmpxchg calls in qspinlock_paravirt.h were replaced by more > > > relaxed versions to improve performance on

Re: [PATCH v3 0/2] iov_iter: allow iov_iter_get_pages_alloc to allocate more pages per call

On Tue, Feb 07, 2017 at 12:35:54PM +0100, Miklos Szeredi wrote: > > Another thing: what guarantees that places in writepages-related paths > > where we store a reference into req->ff won't hit a request with already > > non-NULL ->ff? > > Well, it is set before being sent (queued onto

Re: [PATCH v3 0/2] iov_iter: allow iov_iter_get_pages_alloc to allocate more pages per call

On Tue, Feb 07, 2017 at 12:35:54PM +0100, Miklos Szeredi wrote: > > Another thing: what guarantees that places in writepages-related paths > > where we store a reference into req->ff won't hit a request with already > > non-NULL ->ff? > > Well, it is set before being sent (queued onto

Re: [PATCH V3 3/4] arch/powerpc: Implement Optprobes

Hi Michael, Thank you so much for the review. On Wednesday 01 February 2017 04:23 PM, Michael Ellerman wrote: Anju T Sudhakar writes: Detour buffer contains instructions to create an in memory pt_regs. After the execution of the pre-handler, a call is made for

Re: [PATCH V3 3/4] arch/powerpc: Implement Optprobes

Hi Michael, Thank you so much for the review. On Wednesday 01 February 2017 04:23 PM, Michael Ellerman wrote: Anju T Sudhakar writes: Detour buffer contains instructions to create an in memory pt_regs. After the execution of the pre-handler, a call is made for instruction emulation. The

[-mm PATCH] mm: fix get_user_pages() vs device-dax pud mappings

mic [..] CPU: 0 PID: 21 Comm: rcuos/1 Tainted: G O 4.10.0-rc7-next-20170207+ #944 [..] Call Trace: dump_stack+0x86/0xc3 __warn+0xcb/0xf0 warn_slowpath_fmt+0x5f/0x80 ? rcu_nocb_kthread+0x27a/0x510 ? dax_pmem_percpu_exit+0x50/0x50 [dax_pmem] percpu_ref_switch_to_atomic_

[-mm PATCH] mm: fix get_user_pages() vs device-dax pud mappings

mic [..] CPU: 0 PID: 21 Comm: rcuos/1 Tainted: G O 4.10.0-rc7-next-20170207+ #944 [..] Call Trace: dump_stack+0x86/0xc3 __warn+0xcb/0xf0 warn_slowpath_fmt+0x5f/0x80 ? rcu_nocb_kthread+0x27a/0x510 ? dax_pmem_percpu_exit+0x50/0x50 [dax_pmem] percpu_ref_switch_to_atomic_

[PATCH] thermal: mt8173: minor mtk_thermal.c cleanups

Thermal driver should read TEMP_MSR3 if thermal bank with 4 sensors. However, Currently thermal driver don't need read TEMP_MSR3 since thermal controller only use 3 sensors for each thermal bank. Signed-off-by: Dawei Chien --- drivers/thermal/mtk_thermal.c | 2 +- 1

[PATCH] thermal: mt8173: minor mtk_thermal.c cleanups

Thermal driver should read TEMP_MSR3 if thermal bank with 4 sensors. However, Currently thermal driver don't need read TEMP_MSR3 since thermal controller only use 3 sensors for each thermal bank. Signed-off-by: Dawei Chien --- drivers/thermal/mtk_thermal.c | 2 +- 1 file changed, 1

Re: [PATCH 2/2] spi: s3c64xx: fix potential division by zero

> > This patch fixes '1397922 Division or modulo by zero' from > > scan.coverity.com > > It is a false positive. Yes... sorry for these two spam/patches... they are just fast after holiday "fixes"... please ignore them. Andi

Re: [PATCH 2/2] spi: s3c64xx: fix potential division by zero

> > This patch fixes '1397922 Division or modulo by zero' from > > scan.coverity.com > > It is a false positive. Yes... sorry for these two spam/patches... they are just fast after holiday "fixes"... please ignore them. Andi

[PATCH v2] tools lib traceevent: Robustify do_generate_dynamic_list_file

v2: Accept "W" and "w" symbol options. The dynamic-list-file used to export dynamic symbols introduced in commit e3d09ec8126f ("tools lib traceevent: Export dynamic symbols used by traceevent plugins") is generated without any sort of error checking. I experienced problems due to an old

[PATCH] mm balloon: umount balloon_mnt when remove vb device

With CONFIG_BALLOON_COMPACTION=y, it will mount balloon_mnt for balloon page migration when probe a virtio_balloon device, however do not unmount it when remove the device, fix it. Fixes: b1123ea6d3b3 ("mm: balloon: use general non-lru movable page feature") Signed-off-by: Yisheng Xie

[PATCH v2] tools lib traceevent: Robustify do_generate_dynamic_list_file

v2: Accept "W" and "w" symbol options. The dynamic-list-file used to export dynamic symbols introduced in commit e3d09ec8126f ("tools lib traceevent: Export dynamic symbols used by traceevent plugins") is generated without any sort of error checking. I experienced problems due to an old

[PATCH] mm balloon: umount balloon_mnt when remove vb device

With CONFIG_BALLOON_COMPACTION=y, it will mount balloon_mnt for balloon page migration when probe a virtio_balloon device, however do not unmount it when remove the device, fix it. Fixes: b1123ea6d3b3 ("mm: balloon: use general non-lru movable page feature") Signed-off-by: Yisheng Xie ---

Re: [PATCH v2] drm/mxsfb: fix pixel clock polarity

Dave, Marek, On 2016-12-14 13:25, Marek Vasut wrote: > On 12/14/2016 09:48 PM, Stefan Agner wrote: >> The DRM subsystem specifies the pixel clock polarity from a >> controllers perspective: DRM_BUS_FLAG_PIXDATA_NEGEDGE means >> the controller drives the data on pixel clocks falling edge. >> That

Re: [PATCH v2] drm/mxsfb: fix pixel clock polarity

Dave, Marek, On 2016-12-14 13:25, Marek Vasut wrote: > On 12/14/2016 09:48 PM, Stefan Agner wrote: >> The DRM subsystem specifies the pixel clock polarity from a >> controllers perspective: DRM_BUS_FLAG_PIXDATA_NEGEDGE means >> the controller drives the data on pixel clocks falling edge. >> That

linux-next: build failure after merge of the gpio tree

Hi Linus, After merging the gpio tree, today's linux-next build (arm multi_v7_defconfig) failed like this: drivers/tty/serial/st-asc.c: In function 'asc_set_termios': drivers/tty/serial/st-asc.c:578:12: error: implicit declaration of function 'devm_get_gpiod_from_child'

linux-next: build failure after merge of the gpio tree

Hi Linus, After merging the gpio tree, today's linux-next build (arm multi_v7_defconfig) failed like this: drivers/tty/serial/st-asc.c: In function 'asc_set_termios': drivers/tty/serial/st-asc.c:578:12: error: implicit declaration of function 'devm_get_gpiod_from_child'

Re: [PATCH v9 2/3] MAINTAINERS: add zx2967 thermal drivers to ARM ZTE architecture

Hi Eduardo, On Tue, Feb 07, 2017 at 08:45:39PM -0800, Eduardo Valentin wrote: > > On Tue, Feb 07, 2017 at 08:56:40AM +0800, Baoyou Xie wrote: > > Add the zx2967 thermal drivers as maintained by ARM ZTE > > architecture maintainers, as they're parts of the core IP. > > What kernel version is

Re: [PATCH v9 2/3] MAINTAINERS: add zx2967 thermal drivers to ARM ZTE architecture

Hi Eduardo, On Tue, Feb 07, 2017 at 08:45:39PM -0800, Eduardo Valentin wrote: > > On Tue, Feb 07, 2017 at 08:56:40AM +0800, Baoyou Xie wrote: > > Add the zx2967 thermal drivers as maintained by ARM ZTE > > architecture maintainers, as they're parts of the core IP. > > What kernel version is

Re: v4.9, 4.4-final: 28 bioset threads on small notebook, 36 threads on cellphone

On Tue, Feb 07, 2017 at 09:39:11PM +0100, Pavel Machek wrote: > On Mon 2017-02-06 17:49:06, Kent Overstreet wrote: > > On Mon, Feb 06, 2017 at 04:47:24PM -0900, Kent Overstreet wrote: > > > On Mon, Feb 06, 2017 at 01:53:09PM +0100, Pavel Machek wrote: > > > > Still there on v4.9, 36 threads on

Re: v4.9, 4.4-final: 28 bioset threads on small notebook, 36 threads on cellphone

On Tue, Feb 07, 2017 at 09:39:11PM +0100, Pavel Machek wrote: > On Mon 2017-02-06 17:49:06, Kent Overstreet wrote: > > On Mon, Feb 06, 2017 at 04:47:24PM -0900, Kent Overstreet wrote: > > > On Mon, Feb 06, 2017 at 01:53:09PM +0100, Pavel Machek wrote: > > > > Still there on v4.9, 36 threads on

[PATCH] drivers: usb-misc: sisusbvga: remove dead code

The condition modex % 16 cannot be true when modex value is equal to 640 The condition du & 0xff cannot be true when du value is equal to 0x1400 Addresses-Coverity-Id: 101163 Addresses-Coverity-Id: 744373 Signed-off-by: Gustavo A. R. Silva ---

[PATCH] drivers: usb-misc: sisusbvga: remove dead code

The condition modex % 16 cannot be true when modex value is equal to 640 The condition du & 0xff cannot be true when du value is equal to 0x1400 Addresses-Coverity-Id: 101163 Addresses-Coverity-Id: 744373 Signed-off-by: Gustavo A. R. Silva --- drivers/usb/misc/sisusbvga/sisusb.c | 6 -- 1

Re: [PATCH v9 2/3] MAINTAINERS: add zx2967 thermal drivers to ARM ZTE architecture

On Tue, Feb 07, 2017 at 08:56:40AM +0800, Baoyou Xie wrote: > Add the zx2967 thermal drivers as maintained by ARM ZTE > architecture maintainers, as they're parts of the core IP. What kernel version is this based off? I could not apply this one cleanly. >

Re: [PATCH v9 2/3] MAINTAINERS: add zx2967 thermal drivers to ARM ZTE architecture

On Tue, Feb 07, 2017 at 08:56:40AM +0800, Baoyou Xie wrote: > Add the zx2967 thermal drivers as maintained by ARM ZTE > architecture maintainers, as they're parts of the core IP. What kernel version is this based off? I could not apply this one cleanly. >

Re: [PATCH] time: Remove CONFIG_TIMER_STATS

Hi Kees, [auto build test WARNING on tip/timers/core] [also build test WARNING on v4.10-rc7 next-20170207] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Kees-Cook/time-Remove

Re: [PATCH] time: Remove CONFIG_TIMER_STATS

Hi Kees, [auto build test WARNING on tip/timers/core] [also build test WARNING on v4.10-rc7 next-20170207] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Kees-Cook/time-Remove

Re: [PATCH 2/2] tty: pl011: Work around QDF2400 E44 for earlycon

Hi Cov, The same PL011 driver will be used in virtutal machine, make sure your changes have no side effects in VM. On 02/07/2017 10:07 PM, Timur Tabi wrote: Christopher Covington wrote: The previous change worked around QDF2432v1 and QDF2400v1 SoC erratum 44 for the full-fledged console,

Re: [PATCH 2/2] tty: pl011: Work around QDF2400 E44 for earlycon

Hi Cov, The same PL011 driver will be used in virtutal machine, make sure your changes have no side effects in VM. On 02/07/2017 10:07 PM, Timur Tabi wrote: Christopher Covington wrote: The previous change worked around QDF2432v1 and QDF2400v1 SoC erratum 44 for the full-fledged console,

  1   2   3   4   5   6   7   8   9   10   >