[PATCH] staging:vme Fix use BIT macro

This patch is created to solve the following warning shown by the checkpatch script Warning: Replace all occurences of (1< --- drivers/staging/vme/devices/vme_pio2.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)

[PATCH] staging:vme Fix use BIT macro

This patch is created to solve the following warning shown by the checkpatch script Warning: Replace all occurences of (1< --- drivers/staging/vme/devices/vme_pio2.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/staging/vme/devices/vme_pio2.h

Re: [RFC] sched/fair: Use wake_q length as a hint for wake_wide

On Wed, Sep 20, 2017 at 2:17 PM, Atish Patra wrote: > On 09/20/2017 03:23 PM, Joel Fernandes wrote: >> >> On Wed, Sep 20, 2017 at 2:33 AM, Brendan Jackman >> wrote: >>> >>> >>> On Wed, Sep 20 2017 at 05:06, Joel Fernandes wrote: > > On

Re: [RFC] sched/fair: Use wake_q length as a hint for wake_wide

On Wed, Sep 20, 2017 at 2:17 PM, Atish Patra wrote: > On 09/20/2017 03:23 PM, Joel Fernandes wrote: >> >> On Wed, Sep 20, 2017 at 2:33 AM, Brendan Jackman >> wrote: >>> >>> >>> On Wed, Sep 20 2017 at 05:06, Joel Fernandes wrote: > > On Tue, Sep 19, 2017 at 3:05 AM, Brendan Jackman >

[PATCH] staging:rtl8188eu Fix remove semicolon in do {}while(0)

This patch removes the semicolon at the end of while statement in the do while macro , inorder to avoid it behaving like compound statement. Signed-off-by: Janani Sankara Babu --- drivers/staging/rtl8188eu/core/rtw_security.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH] staging:rtl8188eu Fix remove semicolon in do {}while(0)

This patch removes the semicolon at the end of while statement in the do while macro , inorder to avoid it behaving like compound statement. Signed-off-by: Janani Sankara Babu --- drivers/staging/rtl8188eu/core/rtw_security.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH v2] PM / OPP: Use snprintf to avoid kasprintf and kfree

Use snprintf to avoid unnecessary initializations, avoid calling kfree. Signed-off-by: Arvind Yadav --- changes in v2: Remove kasprintf instead of error checking. drivers/base/power/opp/debugfs.c | 7 +++ 1 file changed, 3 insertions(+), 4

[PATCH v2] PM / OPP: Use snprintf to avoid kasprintf and kfree

Use snprintf to avoid unnecessary initializations, avoid calling kfree. Signed-off-by: Arvind Yadav --- changes in v2: Remove kasprintf instead of error checking. drivers/base/power/opp/debugfs.c | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git

[PATCH] staging:rtl8188eu:hal Fix wrong comparison to False

This patch solves the warning "Using comparison to false is error prone" Signed-off-by: Janani Sankara Babu --- drivers/staging/rtl8188eu/hal/odm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/rtl8188eu/hal/odm.c

[PATCH] staging:rtl8188eu:hal Fix wrong comparison to False

This patch solves the warning "Using comparison to false is error prone" Signed-off-by: Janani Sankara Babu --- drivers/staging/rtl8188eu/hal/odm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/rtl8188eu/hal/odm.c b/drivers/staging/rtl8188eu/hal/odm.c

Re: Memory hotplug regression in 4.13

On Wed, Sep 20, 2017 at 11:29:31AM +0200, Michal Hocko wrote: > Hi, > I am currently at a conference so I will most probably get to this next > week but I will try to ASAP. > > On Tue 19-09-17 11:41:14, Seth Forshee wrote: > > Hi Michal, > > > > I'm seeing oopses in various locations when

Re: Memory hotplug regression in 4.13

On Wed, Sep 20, 2017 at 11:29:31AM +0200, Michal Hocko wrote: > Hi, > I am currently at a conference so I will most probably get to this next > week but I will try to ASAP. > > On Tue 19-09-17 11:41:14, Seth Forshee wrote: > > Hi Michal, > > > > I'm seeing oopses in various locations when

Re: [PATCH] dt-bindings: nand: denali: reduce the register space in the example

Hi. 2017-09-14 18:06 GMT+09:00 Oleksij Rempel : > On 14.09.2017 10:16, Masahiro Yamada wrote: >> >> Hi. >> >> >> 2017-09-14 17:04 GMT+09:00 Oleksij Rempel : >>> >>> Hi, >>> >>> i assume arch/arm/boot/dts/socfpga.dtsi should be update as well. Right? >>

Re: [PATCH] dt-bindings: nand: denali: reduce the register space in the example

Hi. 2017-09-14 18:06 GMT+09:00 Oleksij Rempel : > On 14.09.2017 10:16, Masahiro Yamada wrote: >> >> Hi. >> >> >> 2017-09-14 17:04 GMT+09:00 Oleksij Rempel : >>> >>> Hi, >>> >>> i assume arch/arm/boot/dts/socfpga.dtsi should be update as well. Right? >> >> >> I think so. >> (also

[PATCH v2 2/3] ASoC: fsl-asoc-card: Handle return value of devm_kasprintf

devm_kasprintf() can fail here and we must check its return value. Signed-off-by: Arvind Yadav --- changes in v2: Set return 'ret' to -ENOMEM. sound/soc/fsl/fsl-asoc-card.c | 4 1 file changed, 4 insertions(+) diff --git

[PATCH v2 2/3] ASoC: fsl-asoc-card: Handle return value of devm_kasprintf

devm_kasprintf() can fail here and we must check its return value. Signed-off-by: Arvind Yadav --- changes in v2: Set return 'ret' to -ENOMEM. sound/soc/fsl/fsl-asoc-card.c | 4 1 file changed, 4 insertions(+) diff --git a/sound/soc/fsl/fsl-asoc-card.c

Re: [PATCH] nvme: make controller 'state' sysfs attribute pollable

On Wed, Sep 20, 2017 at 04:59:31PM +0200, Christoph Hellwig wrote: > On Wed, Sep 20, 2017 at 12:40:32PM +0200, Johannes Thumshirn wrote: > > Notify sysfs about changes of a nvme controller so user-space can watch the > > file via poll() or select() in order to react to a state change. > >

Re: [PATCH] nvme: make controller 'state' sysfs attribute pollable

On Wed, Sep 20, 2017 at 04:59:31PM +0200, Christoph Hellwig wrote: > On Wed, Sep 20, 2017 at 12:40:32PM +0200, Johannes Thumshirn wrote: > > Notify sysfs about changes of a nvme controller so user-space can watch the > > file via poll() or select() in order to react to a state change. > >

[PATCH v2 1/2] gpio: brcmstb: Handle return value of devm_kasprintf

devm_kasprintf() can fail here and we must check its return value. Signed-off-by: Arvind Yadav --- changes in v2 : Set return 'err' to -ENOMEM. drivers/gpio/gpio-brcmstb.c | 4 1 file changed, 4 insertions(+) diff --git

[PATCH v2 1/2] gpio: brcmstb: Handle return value of devm_kasprintf

devm_kasprintf() can fail here and we must check its return value. Signed-off-by: Arvind Yadav --- changes in v2 : Set return 'err' to -ENOMEM. drivers/gpio/gpio-brcmstb.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/gpio/gpio-brcmstb.c

Re: [PATCH net-next] net: dsa: use dedicated CPU port

On 09/20/2017 09:28 AM, Vivien Didelot wrote: > Each port in DSA has its own dedicated CPU port currently available in > its parent switch's ds->ports[port].cpu_dp. Use it instead of getting > the unique tree CPU port, which will be deprecated soon. > > Signed-off-by: Vivien Didelot

Re: [PATCH net-next] net: dsa: use dedicated CPU port

On 09/20/2017 09:28 AM, Vivien Didelot wrote: > Each port in DSA has its own dedicated CPU port currently available in > its parent switch's ds->ports[port].cpu_dp. Use it instead of getting > the unique tree CPU port, which will be deprecated soon. > > Signed-off-by: Vivien Didelot > --- >

Re: [PATCH net-next] net: dsa: add port fdb dump

On 09/20/2017 04:32 PM, Vivien Didelot wrote: > Dumping a DSA port's FDB entries is not specific to a DSA slave, so add > a dsa_port_fdb_dump function, similarly to dsa_port_fdb_add and > dsa_port_fdb_del. > > Signed-off-by: Vivien Didelot Reviewed-by:

Re: [PATCH net-next] net: dsa: add port fdb dump

On 09/20/2017 04:32 PM, Vivien Didelot wrote: > Dumping a DSA port's FDB entries is not specific to a DSA slave, so add > a dsa_port_fdb_dump function, similarly to dsa_port_fdb_add and > dsa_port_fdb_del. > > Signed-off-by: Vivien Didelot Reviewed-by: Florian Fainelli -- Florian

Re: [PATCH net-next] net: dsa: better scoping of slave functions

On 09/20/2017 04:31 PM, Vivien Didelot wrote: > A few DSA slave functions take a dsa_slave_priv pointer as first > argument, whereas the scope of the slave.c functions is the slave > net_device structure. Fix this and rename dsa_netpoll_send_skb to > dsa_slave_netpoll_send_skb. > >

Re: [PATCH net-next] net: dsa: better scoping of slave functions

On 09/20/2017 04:31 PM, Vivien Didelot wrote: > A few DSA slave functions take a dsa_slave_priv pointer as first > argument, whereas the scope of the slave.c functions is the slave > net_device structure. Fix this and rename dsa_netpoll_send_skb to > dsa_slave_netpoll_send_skb. > >

Re: [PATCH v2] vfs: introduce UMOUNT_WAIT which waits for umount completion

On 09/21, Al Viro wrote: > On Wed, Sep 20, 2017 at 05:34:09PM -0700, Jaegeuk Kim wrote: > > > flush_delayed_fput() > > > does nothing, the list is empty > > > > how about waiting for workqueue completion here? > > > > > > > > > If all the __fput()s are not

Re: [PATCH v2] vfs: introduce UMOUNT_WAIT which waits for umount completion

On 09/21, Al Viro wrote: > On Wed, Sep 20, 2017 at 05:34:09PM -0700, Jaegeuk Kim wrote: > > > flush_delayed_fput() > > > does nothing, the list is empty > > > > how about waiting for workqueue completion here? > > > > > > > > > If all the __fput()s are not

Re: [PATCH v2 8/8] PM / devfreq: exynos-bus: Register cooling device

Dear all, Please ignore this patch. It has some problem. I'll fix and resend this patch on v2. Chanwoo Choi Samsung Electronics On 2017년 09월 21일 09:33, Chanwoo Choi wrote: > This patch registers the Exynos Bus-Frequency scaling device > as a cooling device of thermal management. > >

Re: [PATCH v2 8/8] PM / devfreq: exynos-bus: Register cooling device

Dear all, Please ignore this patch. It has some problem. I'll fix and resend this patch on v2. Chanwoo Choi Samsung Electronics On 2017년 09월 21일 09:33, Chanwoo Choi wrote: > This patch registers the Exynos Bus-Frequency scaling device > as a cooling device of thermal management. > >

Re:Re: [PATCH net-next] net: Remove useless function skb_header_release

At 2017-09-21 05:30:46, "David Miller" wrote: >From: gfree.w...@vip.163.com >Date: Tue, 19 Sep 2017 22:32:48 +0800 > >> From: Gao Feng >> >> There is no one which would invokes the function skb_header_release. >> So just remove it now. >> >>

Re:Re: [PATCH net-next] net: Remove useless function skb_header_release

At 2017-09-21 05:30:46, "David Miller" wrote: >From: gfree.w...@vip.163.com >Date: Tue, 19 Sep 2017 22:32:48 +0800 > >> From: Gao Feng >> >> There is no one which would invokes the function skb_header_release. >> So just remove it now. >> >> Signed-off-by: Gao Feng > >Networking patches must

Re: [PATCH] powerpc/perf: Fix for core/nest imc call trace on cpuhotplug

Anju T Sudhakar writes: > Nest/core pmu units are enabled only when it is used. A reference count is > maintained for the events which uses the nest/core pmu units. Currently in > *_imc_counters_release function a WARN() is used for notification of any > underflow of ref

Re: [PATCH] powerpc/perf: Fix for core/nest imc call trace on cpuhotplug

Anju T Sudhakar writes: > Nest/core pmu units are enabled only when it is used. A reference count is > maintained for the events which uses the nest/core pmu units. Currently in > *_imc_counters_release function a WARN() is used for notification of any > underflow of ref count. Replace WARN()

Re: [PATCH V6 2/3] dma-mapping: Rework dma_get_cache_alignment()function

Hi, Christoph, I have changed dma_get_cache_alignment's return value, and I don't know whether those drivers want to return ARCH_DMA_MINALIGN unconditionally. So I pass a NULL for those drivers, in order to keep their old behavior. Huacai -- Original -- From:

Re: [PATCH V6 2/3] dma-mapping: Rework dma_get_cache_alignment()function

Hi, Christoph, I have changed dma_get_cache_alignment's return value, and I don't know whether those drivers want to return ARCH_DMA_MINALIGN unconditionally. So I pass a NULL for those drivers, in order to keep their old behavior. Huacai -- Original -- From:

[PATCH v2 5/5] clk: aspeed: Add reset controller

There are some resets that are not associated with gates. These are represented by a reset controller. Signed-off-by: Joel Stanley --- drivers/clk/clk-aspeed.c | 82 +++- include/dt-bindings/clock/aspeed-clock.h | 9 2 files

[PATCH v2 4/5] clk: aspeed: Register gated clocks

The majority of the clocks in the system are gates paired with a reset controller that holds the IP in reset. This borrows from clk_hw_register_gate, but registers two 'gates', one to control the clock enable register and the other to control the reset IP. This allows us to enforce the ordering:

[PATCH v2 3/5] clk: aspeed: Add platform driver and register PLLs

This registers a platform driver to set up all of the non-core clocks. The clocks that have configurable rates are now registered. Signed-off-by: Joel Stanley --- drivers/clk/clk-aspeed.c | 129 +++ 1 file changed, 129 insertions(+)

[PATCH v2 5/5] clk: aspeed: Add reset controller

There are some resets that are not associated with gates. These are represented by a reset controller. Signed-off-by: Joel Stanley --- drivers/clk/clk-aspeed.c | 82 +++- include/dt-bindings/clock/aspeed-clock.h | 9 2 files changed, 90

[PATCH v2 4/5] clk: aspeed: Register gated clocks

The majority of the clocks in the system are gates paired with a reset controller that holds the IP in reset. This borrows from clk_hw_register_gate, but registers two 'gates', one to control the clock enable register and the other to control the reset IP. This allows us to enforce the ordering:

[PATCH v2 3/5] clk: aspeed: Add platform driver and register PLLs

This registers a platform driver to set up all of the non-core clocks. The clocks that have configurable rates are now registered. Signed-off-by: Joel Stanley --- drivers/clk/clk-aspeed.c | 129 +++ 1 file changed, 129 insertions(+) diff --git

[PATCH v2 1/5] clk: Add clock driver for ASPEED BMC SoCs

This adds the stub of a driver for the ASPEED SoCs. The clocks are defined and the static registration is set up. Signed-off-by: Joel Stanley --- drivers/clk/Kconfig | 12 +++ drivers/clk/Makefile | 1 + drivers/clk/clk-aspeed.c

[PATCH v2 1/5] clk: Add clock driver for ASPEED BMC SoCs

This adds the stub of a driver for the ASPEED SoCs. The clocks are defined and the static registration is set up. Signed-off-by: Joel Stanley --- drivers/clk/Kconfig | 12 +++ drivers/clk/Makefile | 1 + drivers/clk/clk-aspeed.c | 162

[PATCH v2 0/5] clk: Add Aspeed clock driver

This driver supports the ast2500, ast2400 (and derivative) BMC SoCs from Aspeed. This is version two of the series. Version one contained two patches; an update to the binding document and a single patch for the driver. Lee has merged the bindings change, so that is dropped from this series, and

[PATCH v2 2/5] clk: aspeed: Register core clocks

This registers the core clocks; those which are required to calculate the rate of the timer periperhal so the system can load a clocksource driver. Signed-off-by: Joel Stanley --- drivers/clk/clk-aspeed.c | 152 ++- 1 file changed, 149

[PATCH v2 2/5] clk: aspeed: Register core clocks

This registers the core clocks; those which are required to calculate the rate of the timer periperhal so the system can load a clocksource driver. Signed-off-by: Joel Stanley --- drivers/clk/clk-aspeed.c | 152 ++- 1 file changed, 149 insertions(+),

[PATCH v2 0/5] clk: Add Aspeed clock driver

This driver supports the ast2500, ast2400 (and derivative) BMC SoCs from Aspeed. This is version two of the series. Version one contained two patches; an update to the binding document and a single patch for the driver. Lee has merged the bindings change, so that is dropped from this series, and

[git pull][vfs.git] a couple of fixes

A couple of regression fixes, one for this merge window, one for the previous cycle. The following changes since commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e: Linux 4.14-rc1 (2017-09-16 15:47:51 -0700) are available in the git repository at:

[git pull][vfs.git] a couple of fixes

A couple of regression fixes, one for this merge window, one for the previous cycle. The following changes since commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e: Linux 4.14-rc1 (2017-09-16 15:47:51 -0700) are available in the git repository at:

linux-next: Tree for Sep 21

Hi all, Changes since 20170920: Linus' tree lost its build failure. The sound-asoc tree lost its build failure. Non-merge commits (relative to Linus' tree): 1337 1200 files changed, 49498 insertions(+), 15649 deletions

linux-next: Tree for Sep 21

Hi all, Changes since 20170920: Linus' tree lost its build failure. The sound-asoc tree lost its build failure. Non-merge commits (relative to Linus' tree): 1337 1200 files changed, 49498 insertions(+), 15649 deletions

Re: [PATCH] mpt3sas: downgrade full copy_from_user to access_ok check

> On Sep 20, 2017, at 11:26 PM, Al Viro wrote: > > On Tue, Sep 19, 2017 at 11:11:11PM -0400, Meng Xu wrote: >> Since right after the user copy, we are going to >> memset(, 0, sizeof(karg)), I guess an access_ok check is enough? > > access_ok() is *NOT* "will

Re: [PATCH] mpt3sas: downgrade full copy_from_user to access_ok check

> On Sep 20, 2017, at 11:26 PM, Al Viro wrote: > > On Tue, Sep 19, 2017 at 11:11:11PM -0400, Meng Xu wrote: >> Since right after the user copy, we are going to >> memset(, 0, sizeof(karg)), I guess an access_ok check is enough? > > access_ok() is *NOT* "will copy_from_user() succeed?" Not

Re: [lkp-robot] [drivers] ceed73a2cf: drivers/net/ethernet/qualcomm/rmnet/rmnet_config.c:#suspicious_rcu_dereference_check()usage

On 2017-09-19 19:55, kernel test robot wrote: FYI, we noticed the following commit: commit: ceed73a2cf4aff2921802aa3d21d45280677547d ("drivers: net: ethernet: qualcomm: rmnet: Initial implementation") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master in testcase: boot on

Re: [lkp-robot] [drivers] ceed73a2cf: drivers/net/ethernet/qualcomm/rmnet/rmnet_config.c:#suspicious_rcu_dereference_check()usage

On 2017-09-19 19:55, kernel test robot wrote: FYI, we noticed the following commit: commit: ceed73a2cf4aff2921802aa3d21d45280677547d ("drivers: net: ethernet: qualcomm: rmnet: Initial implementation") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master in testcase: boot on

Re: [PATCH] mpt3sas: downgrade full copy_from_user to access_ok check

On Tue, Sep 19, 2017 at 11:11:11PM -0400, Meng Xu wrote: > Since right after the user copy, we are going to > memset(, 0, sizeof(karg)), I guess an access_ok check is enough? access_ok() is *NOT* "will copy_from_user() succeed?" Not even close. On a bunch of architectures (sparc64, for one)

Re: [PATCH] mpt3sas: downgrade full copy_from_user to access_ok check

On Tue, Sep 19, 2017 at 11:11:11PM -0400, Meng Xu wrote: > Since right after the user copy, we are going to > memset(, 0, sizeof(karg)), I guess an access_ok check is enough? access_ok() is *NOT* "will copy_from_user() succeed?" Not even close. On a bunch of architectures (sparc64, for one)

Re: [PATCH 1/2] gpio: brcmstb: Handle return value of devm_kasprintf

On Wed, Sep 20, 2017 at 12:13 AM, Arvind Yadav wrote: > devm_kasprintf() can fail here and we must check its return value. > > Signed-off-by: Arvind Yadav > --- > drivers/gpio/gpio-brcmstb.c | 3 +++ > 1 file changed, 3 insertions(+) > >

Re: [PATCH 1/2] gpio: brcmstb: Handle return value of devm_kasprintf

On Wed, Sep 20, 2017 at 12:13 AM, Arvind Yadav wrote: > devm_kasprintf() can fail here and we must check its return value. > > Signed-off-by: Arvind Yadav > --- > drivers/gpio/gpio-brcmstb.c | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/drivers/gpio/gpio-brcmstb.c

Re: Read-only `slaves` with shared subtrees?

On Wed, Sep 20, 2017 at 5:39 PM, Ram Pai wrote: > Anyway; so something like this should be possible without breaking > existing semantics. > > mount -o bind,remount,ro /mnt > mount --make-pass-on-access /mnt > > anything that gets mounted under /mnt will inherit the > 'ro'

Re: Read-only `slaves` with shared subtrees?

On Wed, Sep 20, 2017 at 5:39 PM, Ram Pai wrote: > Anyway; so something like this should be possible without breaking > existing semantics. > > mount -o bind,remount,ro /mnt > mount --make-pass-on-access /mnt > > anything that gets mounted under /mnt will inherit the > 'ro' attribute from its

[PATCH v2] block: consider merge of segments when merge bio into rq

When account the nr_phys_segments during merging bios into rq, only consider segments merging in individual bio but not all the bios in a rq. This leads to the bigger nr_phys_segments of rq than the real one when the segments of bios in rq are contiguous and mergeable. The nr_phys_segments of rq

[PATCH v2] block: consider merge of segments when merge bio into rq

When account the nr_phys_segments during merging bios into rq, only consider segments merging in individual bio but not all the bios in a rq. This leads to the bigger nr_phys_segments of rq than the real one when the segments of bios in rq are contiguous and mergeable. The nr_phys_segments of rq

Re: [PATCH] block: consider merge of segments when merge bio into rq

On 09/21/2017 09:29 AM, Christoph Hellwig wrote: > So the check change here looks good to me. > > I don't like like the duplicate code, can you look into sharing > the new segment checks between the two functions and the existing > instance in ll_merge_requests_fn by passing say two struct bio

Re: [PATCH] block: consider merge of segments when merge bio into rq

On 09/21/2017 09:29 AM, Christoph Hellwig wrote: > So the check change here looks good to me. > > I don't like like the duplicate code, can you look into sharing > the new segment checks between the two functions and the existing > instance in ll_merge_requests_fn by passing say two struct bio

[lkp-robot] [blk] 47e0fb461f: BUG:unable_to_handle_kernel

FYI, we noticed the following commit: commit: 47e0fb461fca1a68a566c82fcc006cc787312d8c ("blk: make the bioset rescue_workqueue optional.") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master in testcase: trinity with following parameters: runtime: 300s

[lkp-robot] [blk] 47e0fb461f: BUG:unable_to_handle_kernel

FYI, we noticed the following commit: commit: 47e0fb461fca1a68a566c82fcc006cc787312d8c ("blk: make the bioset rescue_workqueue optional.") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master in testcase: trinity with following parameters: runtime: 300s

RE: [PATCHv2 0/3] arm64: dts: ls1012a: add the DTS node for DSPI support

Hi Shawn, > -Original Message- > From: Shawn Guo [mailto:shawn...@kernel.org] > Sent: 2017年9月20日 22:11 > To: Z.q. Hou > Cc: linux-arm-ker...@lists.infradead.org; devicet...@vger.kernel.org; > linux-kernel@vger.kernel.org; dw...@infradead.org; robh...@kernel.org; >

RE: [PATCHv2 0/3] arm64: dts: ls1012a: add the DTS node for DSPI support

Hi Shawn, > -Original Message- > From: Shawn Guo [mailto:shawn...@kernel.org] > Sent: 2017年9月20日 22:11 > To: Z.q. Hou > Cc: linux-arm-ker...@lists.infradead.org; devicet...@vger.kernel.org; > linux-kernel@vger.kernel.org; dw...@infradead.org; robh...@kernel.org; > mark.rutl...@arm.com;

Re: [PATCH v2] vfs: introduce UMOUNT_WAIT which waits for umount completion

On Wed, Sep 20, 2017 at 05:34:09PM -0700, Jaegeuk Kim wrote: > > flush_delayed_fput() > > does nothing, the list is empty > > how about waiting for workqueue completion here? > > > > > If all the __fput()s are not finished, do_umount() will return

Re: [PATCH v2] vfs: introduce UMOUNT_WAIT which waits for umount completion

On Wed, Sep 20, 2017 at 05:34:09PM -0700, Jaegeuk Kim wrote: > > flush_delayed_fput() > > does nothing, the list is empty > > how about waiting for workqueue completion here? > > > > > If all the __fput()s are not finished, do_umount() will return

[PATCH v2 2/2] security: keys: Replace time_t with time64_t for struct key_preparsed_payload

The 'struct key_preparsed_payload' will use 'time_t' which we will try to remove in the kernel, since 'time_t' is not year 2038 safe on 32bits systems. Thus this patch replaces 'time_t' with 'time64_t' which is year 2038 safe on 32 bits system for 'struct key_preparsed_payload', moreover we

[PATCH v2 2/2] security: keys: Replace time_t with time64_t for struct key_preparsed_payload

The 'struct key_preparsed_payload' will use 'time_t' which we will try to remove in the kernel, since 'time_t' is not year 2038 safe on 32bits systems. Thus this patch replaces 'time_t' with 'time64_t' which is year 2038 safe on 32 bits system for 'struct key_preparsed_payload', moreover we

[PATCH v2 1/2] security: keys: Replace time_t/timespec with time64_t

The 'struct key' will use 'time_t' which we try to remove in the kernel, since 'time_t' is not year 2038 safe on 32bit systems. Also the 'struct keyring_search_context' will use 'timespec' type to record current time, which is also not year 2038 safe on 32bit systems. Thus this patch replaces

[PATCH v2 1/2] security: keys: Replace time_t/timespec with time64_t

The 'struct key' will use 'time_t' which we try to remove in the kernel, since 'time_t' is not year 2038 safe on 32bit systems. Also the 'struct keyring_search_context' will use 'timespec' type to record current time, which is also not year 2038 safe on 32bit systems. Thus this patch replaces

[PATCH v2 0/2] Fix y2038 issues for security/keys subsystem

Since 'time_t', 'timeval' and 'timespec' types are not year 2038 safe on 32 bits system, this patchset tries to fix this issues for security/keys subsystem. Changes since v1: - Add reviewed tag from Arnd. - Drop Patch 3 which had been merged into kernel 4.14 by David. Baolin Wang (2):

[PATCH v2 0/2] Fix y2038 issues for security/keys subsystem

Since 'time_t', 'timeval' and 'timespec' types are not year 2038 safe on 32 bits system, this patchset tries to fix this issues for security/keys subsystem. Changes since v1: - Add reviewed tag from Arnd. - Drop Patch 3 which had been merged into kernel 4.14 by David. Baolin Wang (2):

Re: [RFC][PATCH v2 7/7] checkpatch: add pF/pf deprecation warning

On Thu, 2017-09-21 at 09:27 +0900, Sergey Senozhatsky wrote: > On (09/20/17 10:38), Joe Perches wrote: > > On Thu, 2017-09-21 at 01:29 +0900, Sergey Senozhatsky wrote: > > > We deprecated '%pF/%pf' printk specifiers, since '%pS/%ps' is now smart > > > enough to handle function pointer dereference

Re: [RFC][PATCH v2 7/7] checkpatch: add pF/pf deprecation warning

On Thu, 2017-09-21 at 09:27 +0900, Sergey Senozhatsky wrote: > On (09/20/17 10:38), Joe Perches wrote: > > On Thu, 2017-09-21 at 01:29 +0900, Sergey Senozhatsky wrote: > > > We deprecated '%pF/%pf' printk specifiers, since '%pS/%ps' is now smart > > > enough to handle function pointer dereference

Re: [RFC RESEND 3/3] arm: dts: add Hi3521A dts

On Thu, Sep 21, 2017 at 01:08:39AM +, Rob Herring wrote: > On Wed, Sep 20, 2017 at 6:04 PM, Marty E. Plummer > wrote: > > On Wed, Sep 20, 2017 at 08:53:03PM +, Rob Herring wrote: > >> On Sun, Sep 17, 2017 at 03:23:27AM -0500, Marty E. Plummer wrote: > >> > Add

Re: [RFC RESEND 3/3] arm: dts: add Hi3521A dts

On Thu, Sep 21, 2017 at 01:08:39AM +, Rob Herring wrote: > On Wed, Sep 20, 2017 at 6:04 PM, Marty E. Plummer > wrote: > > On Wed, Sep 20, 2017 at 08:53:03PM +, Rob Herring wrote: > >> On Sun, Sep 17, 2017 at 03:23:27AM -0500, Marty E. Plummer wrote: > >> > Add hi3521a.dtsi and

RE: [PATCH 1/7] PM / OPP: Add platform specific set_clk function

> -Original Message- > From: Viresh Kumar [mailto:viresh.ku...@linaro.org] > Sent: Thursday, September 21, 2017 4:31 AM > To: Dong Aisheng > Cc: A.s. Dong; linux...@vger.kernel.org; linux-kernel@vger.kernel.org; > linux-arm-ker...@lists.infradead.org; sb...@codeaurora.org; >

RE: [PATCH 1/7] PM / OPP: Add platform specific set_clk function

> -Original Message- > From: Viresh Kumar [mailto:viresh.ku...@linaro.org] > Sent: Thursday, September 21, 2017 4:31 AM > To: Dong Aisheng > Cc: A.s. Dong; linux...@vger.kernel.org; linux-kernel@vger.kernel.org; > linux-arm-ker...@lists.infradead.org; sb...@codeaurora.org; >

Re: [PATCH 2/5] nvmem: mtk-efuse: use stack for nvmem_config instead of malloc'ing it

Hi Sean, 2017-09-21 1:32 GMT+09:00 Sean Wang : > Hi, Masahiro > > For maintainability, I felt it's better if we use the same way to > register nvmem as that most drivers does under nvmem usually using > static structure. Otherwise, they should also be changed to use the >

Re: [PATCH 2/5] nvmem: mtk-efuse: use stack for nvmem_config instead of malloc'ing it

Hi Sean, 2017-09-21 1:32 GMT+09:00 Sean Wang : > Hi, Masahiro > > For maintainability, I felt it's better if we use the same way to > register nvmem as that most drivers does under nvmem usually using > static structure. Otherwise, they should also be changed to use the > one-time data in stack

Re: 4.13 breaks suspend to ram wakeup

Hi Ming, > So could you share us how often it is triggered? and what is your underlying > disk behind dm-crypt? It is triggered *every* time I suspend. Underlying disk is scsi 1:0:0:0: Direct-Access ATA WDC WD10JPVX-08J 1A07 PQ: 0 ANSI: 5 I checked the values in

Re: 4.13 breaks suspend to ram wakeup

Hi Ming, > So could you share us how often it is triggered? and what is your underlying > disk behind dm-crypt? It is triggered *every* time I suspend. Underlying disk is scsi 1:0:0:0: Direct-Access ATA WDC WD10JPVX-08J 1A07 PQ: 0 ANSI: 5 I checked the values in

Re: [Patch v3 1/3] ipv4: Namespaceify tcp_fastopen knob

> On 2017年9月21日, at 上午5:22, David Miller wrote: > > From: Haishuang Yan > Date: Tue, 19 Sep 2017 17:38:14 +0800 > >> -if ((sysctl_tcp_fastopen & TFO_SERVER_WO_SOCKOPT1) && >> -(sysctl_tcp_fastopen &

Re: [Patch v3 1/3] ipv4: Namespaceify tcp_fastopen knob

> On 2017年9月21日, at 上午5:22, David Miller wrote: > > From: Haishuang Yan > Date: Tue, 19 Sep 2017 17:38:14 +0800 > >> -if ((sysctl_tcp_fastopen & TFO_SERVER_WO_SOCKOPT1) && >> -(sysctl_tcp_fastopen & TFO_SERVER_ENABLE) && >> +tcp_fastopen =

[PATCH v2] mmc: dt-bindings: Add reg/source_cg/latch-ck for Mediatek MMC bindings

Change the comptiable for support of multi-platform Add description for reg Add description for source_cg Add description for mediatek,latch-ck Note that source_cg and mediatek,latch-ck are optional for some projects, eg, MT2701 do not have source_cg, and MT2712 do not need mediatek,latch-ck

[PATCH v2] mmc: dt-bindings: Add reg/source_cg/latch-ck for Mediatek MMC bindings

Change the comptiable for support of multi-platform Add description for reg Add description for source_cg Add description for mediatek,latch-ck Note that source_cg and mediatek,latch-ck are optional for some projects, eg, MT2701 do not have source_cg, and MT2712 do not need mediatek,latch-ck

Re: [REGRESSION] Warning in tcp_fastretrans_alert() of net/ipv4/tcp_input.c

> Hello. > > Since, IIRC, v4.11, there is some regression in TCP stack resulting in the > warning shown below. Most of the time it is harmless, but rarely it just > causes either freeze or (I believe, this is related too) panic in > tcp_sacktag_walk() (because sk_buff passed to this function is

Re: [REGRESSION] Warning in tcp_fastretrans_alert() of net/ipv4/tcp_input.c

> Hello. > > Since, IIRC, v4.11, there is some regression in TCP stack resulting in the > warning shown below. Most of the time it is harmless, but rarely it just > causes either freeze or (I believe, this is related too) panic in > tcp_sacktag_walk() (because sk_buff passed to this function is

Re: powerpc/sysrq: Fix oops whem ppmu is not registered

On Tue, 2017-09-19 at 06:17:06 UTC, Ravi Bangoria wrote: > Kernel crashes if power pmu is not registered and user tries to dump > regs with 'echo p > /proc/sysrq-trigger'. Sample log: > > Unable to handle kernel paging request for data at address 0x0008 > Faulting instruction address:

Re: powerpc/powernv: Clear LPCR[PECE1] via stop-api only for deep state offline

On Thu, 2017-08-31 at 11:47:41 UTC, "Gautham R. Shenoy" wrote: > From: "Gautham R. Shenoy" > > commit 24be85a23d1f ("powerpc/powernv: Clear PECE1 in LPCR via > stop-api only on Hotplug") clears the PECE1 bit of the LPCR via > stop-api during CPU-Hotplug to prevent wakeup

Re: powerpc/sysrq: Fix oops whem ppmu is not registered

On Tue, 2017-09-19 at 06:17:06 UTC, Ravi Bangoria wrote: > Kernel crashes if power pmu is not registered and user tries to dump > regs with 'echo p > /proc/sysrq-trigger'. Sample log: > > Unable to handle kernel paging request for data at address 0x0008 > Faulting instruction address:

Re: powerpc/powernv: Clear LPCR[PECE1] via stop-api only for deep state offline

On Thu, 2017-08-31 at 11:47:41 UTC, "Gautham R. Shenoy" wrote: > From: "Gautham R. Shenoy" > > commit 24be85a23d1f ("powerpc/powernv: Clear PECE1 in LPCR via > stop-api only on Hotplug") clears the PECE1 bit of the LPCR via > stop-api during CPU-Hotplug to prevent wakeup due to a decrementer on

Re: [PATCH v2] mm: introduce validity check on vm dirtiness settings

2017-09-20 23:33 GMT+08:00 Jan Kara : > On Tue 19-09-17 19:48:00, Yafang Shao wrote: >> 2017-09-19 16:35 GMT+08:00 Jan Kara : >> > On Tue 19-09-17 06:53:00, Yafang Shao wrote: >> >> + if (vm_dirty_bytes == 0 && vm_dirty_ratio == 0 && >> >> +

Re: usb/hid: slab-out-of-bounds read in usbhid_parse

Hi Alan 2017-09-21 0:50 GMT+09:00 Alan Stern : > On Wed, 20 Sep 2017, Kim Jaejoong wrote: > >> To. usb & input guys. >> >> While dig this report, i was wondering about bNumDescriptors in HID >> descriptor. >> HID document from usb.org said, 'this number must be at

  1   2   3   4   5   6   7   8   9   10   >