Re: [PATCH 3.18 00/24] 3.18.107-stable review

On Fri, Apr 27, 2018 at 11:00:41PM +0700, Dede Dindin Qudsy wrote: > > > On 27/04/18 20:57, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 3.18.107 release. > > There are 24 patches in this series, all will be posted as a response > > to this one. If anyone

Re: [PATCH 3.18 00/24] 3.18.107-stable review

On Fri, Apr 27, 2018 at 11:00:41PM +0700, Dede Dindin Qudsy wrote: > > > On 27/04/18 20:57, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 3.18.107 release. > > There are 24 patches in this series, all will be posted as a response > > to this one. If anyone

Re: [PATCH 4.16 00/81] 4.16.6-stable review

On Fri, Apr 27, 2018 at 03:41:14PM -0500, Dan Rue wrote: > On Fri, Apr 27, 2018 at 03:58:02PM +0200, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.16.6 release. > > There are 81 patches in this series, all will be posted as a response > > to this one. If

Re: [PATCH 4.16 00/81] 4.16.6-stable review

On Fri, Apr 27, 2018 at 03:41:14PM -0500, Dan Rue wrote: > On Fri, Apr 27, 2018 at 03:58:02PM +0200, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.16.6 release. > > There are 81 patches in this series, all will be posted as a response > > to this one. If

Re: [PATCH 4.14 41/80] Revert "microblaze: fix endian handling"

On Fri, Apr 27, 2018 at 09:25:24AM -0700, Guenter Roeck wrote: > On Fri, Apr 27, 2018 at 03:58:34PM +0200, Greg Kroah-Hartman wrote: > > 4.14-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: Greg Kroah-Hartman

Re: [PATCH 4.14 41/80] Revert "microblaze: fix endian handling"

On Fri, Apr 27, 2018 at 09:25:24AM -0700, Guenter Roeck wrote: > On Fri, Apr 27, 2018 at 03:58:34PM +0200, Greg Kroah-Hartman wrote: > > 4.14-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: Greg Kroah-Hartman > > > > This reverts

[PATCH v2 1/2] arm64: dts: Add msm8998 SoC and MTP board support

From: Joonwoo Park Add initial device tree support for the Qualcomm MSM8998 SoC and MTP8998 evaluation board. Signed-off-by: Joonwoo Park Signed-off-by: Imran Khan Signed-off-by: Rajendra Nayak

[PATCH v2 1/2] arm64: dts: Add msm8998 SoC and MTP board support

From: Joonwoo Park Add initial device tree support for the Qualcomm MSM8998 SoC and MTP8998 evaluation board. Signed-off-by: Joonwoo Park Signed-off-by: Imran Khan Signed-off-by: Rajendra Nayak [bjorn: Restructured, removed its node and moved to SPDX headers] Signed-off-by: Bjorn Andersson

[PATCH v2 2/2] arm64: dts: qcom: msm8998: Add rpm and regulators for MTP

This adds the rpm and rpm regulators to the msm8998 platform and mtp. Signed-off-by: Bjorn Andersson --- arch/arm64/boot/dts/qcom/msm8998-mtp.dtsi | 142 ++ arch/arm64/boot/dts/qcom/msm8998.dtsi | 83 + 2 files

[PATCH v2 2/2] arm64: dts: qcom: msm8998: Add rpm and regulators for MTP

This adds the rpm and rpm regulators to the msm8998 platform and mtp. Signed-off-by: Bjorn Andersson --- arch/arm64/boot/dts/qcom/msm8998-mtp.dtsi | 142 ++ arch/arm64/boot/dts/qcom/msm8998.dtsi | 83 + 2 files changed, 225 insertions(+) diff

Re: [PATCH] mm: memory_hotplug: use put_device() if device_register fail

On Friday 27 April 2018 08:26 PM, Michal Hocko wrote: On Thu 26-04-18 21:12:09, Arvind Yadav wrote: if device_register() returned an error. Always use put_device() to give up the initialized reference and release allocated memory. Is this patch correct? The docummentation says * NOTE:

Re: [PATCH] mm: memory_hotplug: use put_device() if device_register fail

On Friday 27 April 2018 08:26 PM, Michal Hocko wrote: On Thu 26-04-18 21:12:09, Arvind Yadav wrote: if device_register() returned an error. Always use put_device() to give up the initialized reference and release allocated memory. Is this patch correct? The docummentation says * NOTE:

Re: [PATCH] bpf: fix misaligned access for BPF_PROG_TYPE_PERF_EVENT program type on x86_32 platform

On Sat, Apr 28, 2018 at 01:33:15AM +0200, Daniel Borkmann wrote: > On 04/28/2018 12:48 AM, Alexei Starovoitov wrote: > > On Thu, Apr 26, 2018 at 05:57:49PM +0800, Wang YanQing wrote: > >> All the testcases for BPF_PROG_TYPE_PERF_EVENT program type in > >> test_verifier(kselftest) report below

Re: [PATCH] bpf: fix misaligned access for BPF_PROG_TYPE_PERF_EVENT program type on x86_32 platform

On Sat, Apr 28, 2018 at 01:33:15AM +0200, Daniel Borkmann wrote: > On 04/28/2018 12:48 AM, Alexei Starovoitov wrote: > > On Thu, Apr 26, 2018 at 05:57:49PM +0800, Wang YanQing wrote: > >> All the testcases for BPF_PROG_TYPE_PERF_EVENT program type in > >> test_verifier(kselftest) report below

Re: copy_file_range and user space tools to do copy fastest

On Sat, Apr 28, 2018 at 12:18 AM, Andreas Dilger wrote: > On Apr 27, 2018, at 5:41 PM, Eric Biggers wrote: >> >> On Fri, Apr 27, 2018 at 01:45:40PM -0600, Andreas Dilger wrote: >>> On Apr 27, 2018, at 12:25 PM, Steve French wrote:

Re: copy_file_range and user space tools to do copy fastest

On Sat, Apr 28, 2018 at 12:18 AM, Andreas Dilger wrote: > On Apr 27, 2018, at 5:41 PM, Eric Biggers wrote: >> >> On Fri, Apr 27, 2018 at 01:45:40PM -0600, Andreas Dilger wrote: >>> On Apr 27, 2018, at 12:25 PM, Steve French wrote: Are there any user space tools (other than our test

Re: WARNING in perf_trace_buf_alloc (2)

On Sat, Apr 21, 2018 at 12:37:01PM -0700, Eric Biggers wrote: > [+bpf maintainers and netdev] > > On Mon, Nov 06, 2017 at 03:56:01AM -0800, syzbot wrote: > > Hello, > > > > syzkaller hit the following crash on > > 5cb0512c02ecd7e6214e912e4c150f4219ac78e0 > >

Re: WARNING in perf_trace_buf_alloc (2)

On Sat, Apr 21, 2018 at 12:37:01PM -0700, Eric Biggers wrote: > [+bpf maintainers and netdev] > > On Mon, Nov 06, 2017 at 03:56:01AM -0800, syzbot wrote: > > Hello, > > > > syzkaller hit the following crash on > > 5cb0512c02ecd7e6214e912e4c150f4219ac78e0 > >

Re: copy_file_range and user space tools to do copy fastest

On Apr 27, 2018, at 5:41 PM, Eric Biggers wrote: > > On Fri, Apr 27, 2018 at 01:45:40PM -0600, Andreas Dilger wrote: >> On Apr 27, 2018, at 12:25 PM, Steve French wrote: >>> >>> Are there any user space tools (other than our test tools and xfs_io >>>

Re: copy_file_range and user space tools to do copy fastest

On Apr 27, 2018, at 5:41 PM, Eric Biggers wrote: > > On Fri, Apr 27, 2018 at 01:45:40PM -0600, Andreas Dilger wrote: >> On Apr 27, 2018, at 12:25 PM, Steve French wrote: >>> >>> Are there any user space tools (other than our test tools and xfs_io >>> etc.) that support copy_file_range? Looks

Re: [PATCH v1 4/4] mhi_bus: dev: uci: add user space interface driver

Hi Sujeev, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on linus/master] [also build test WARNING on v4.17-rc2 next-20180426] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v1 4/4] mhi_bus: dev: uci: add user space interface driver

Hi Sujeev, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on linus/master] [also build test WARNING on v4.17-rc2 next-20180426] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH] mhi_bus: dev: uci: fix semicolon.cocci warnings

From: Fengguang Wu drivers/bus/mhi/devices/mhi_uci.c:556:2-3: Unneeded semicolon Remove unneeded semicolon. Generated by: scripts/coccinelle/misc/semicolon.cocci Fixes: 2064c7ebc5cb ("mhi_bus: dev: uci: add user space interface driver") CC: Sujeev Dias

[PATCH] mhi_bus: dev: uci: fix semicolon.cocci warnings

From: Fengguang Wu drivers/bus/mhi/devices/mhi_uci.c:556:2-3: Unneeded semicolon Remove unneeded semicolon. Generated by: scripts/coccinelle/misc/semicolon.cocci Fixes: 2064c7ebc5cb ("mhi_bus: dev: uci: add user space interface driver") CC: Sujeev Dias Signed-off-by: Fengguang Wu ---

Re: [PATCH 4.14 00/80] 4.14.38-stable review

On Fri, Apr 27, 2018 at 12:33:27PM -0700, Nathan Chancellor wrote: > On Fri, Apr 27, 2018 at 03:57:53PM +0200, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.14.38 release. > > There are 80 patches in this series, all will be posted as a response > > to this

Re: [PATCH] dmaengine: stm32-mdma: fix spelling mistake: "avalaible" -> "available"

On Fri, Apr 27, 2018 at 08:24:31PM +0100, Colin King wrote: > From: Colin Ian King > > Trivial fix to spelling mistake in dev_err error message text Applied, thanks -- ~Vinod

Re: [PATCH 4.14 00/80] 4.14.38-stable review

On Fri, Apr 27, 2018 at 12:33:27PM -0700, Nathan Chancellor wrote: > On Fri, Apr 27, 2018 at 03:57:53PM +0200, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.14.38 release. > > There are 80 patches in this series, all will be posted as a response > > to this

Re: [PATCH] dmaengine: stm32-mdma: fix spelling mistake: "avalaible" -> "available"

On Fri, Apr 27, 2018 at 08:24:31PM +0100, Colin King wrote: > From: Colin Ian King > > Trivial fix to spelling mistake in dev_err error message text Applied, thanks -- ~Vinod

Re: [PATCH v2] dmaengine: axi-dmac: Request IRQ with IRQF_SHARED

On Fri, Apr 27, 2018 at 05:18:29PM +0200, Lars-Peter Clausen wrote: > On 04/27/2018 05:15 PM, Moritz Fischer wrote: > > Hi Vinod, > > > > On Fri, Apr 27, 2018 at 12:08 AM, Vinod Koul wrote: > >> On Fri, Apr 27, 2018 at 08:53:39AM +0200, Lars-Peter Clausen wrote: > >>> On

Re: [PATCH v2] dmaengine: axi-dmac: Request IRQ with IRQF_SHARED

On Fri, Apr 27, 2018 at 05:18:29PM +0200, Lars-Peter Clausen wrote: > On 04/27/2018 05:15 PM, Moritz Fischer wrote: > > Hi Vinod, > > > > On Fri, Apr 27, 2018 at 12:08 AM, Vinod Koul wrote: > >> On Fri, Apr 27, 2018 at 08:53:39AM +0200, Lars-Peter Clausen wrote: > >>> On 04/27/2018 07:11 AM,

Re: [PATCH] mm: provide a fallback for PAGE_KERNEL_RO for architectures

On Fri, Apr 27, 2018 at 05:15:26PM -0700, Luis R. Rodriguez wrote: > Some architectures do not define PAGE_KERNEL_RO, best we can do > for them is to provide a fallback onto PAGE_KERNEL. Remove the > hack from the firmware loader and move it onto the asm-generic > header, and document while at it

Re: [PATCH] mm: provide a fallback for PAGE_KERNEL_RO for architectures

On Fri, Apr 27, 2018 at 05:15:26PM -0700, Luis R. Rodriguez wrote: > Some architectures do not define PAGE_KERNEL_RO, best we can do > for them is to provide a fallback onto PAGE_KERNEL. Remove the > hack from the firmware loader and move it onto the asm-generic > header, and document while at it

Re: [PATCH 3.18 00/24] 3.18.107-stable review

On Fri, Apr 27, 2018 at 12:12:32PM -0600, Shuah Khan wrote: > On 04/27/2018 07:57 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 3.18.107 release. > > There are 24 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH 3.18 00/24] 3.18.107-stable review

On Sat, Apr 28, 2018 at 03:03:04AM +0530, Harsh Shandilya wrote: > On 27 April 2018 7:27:35 PM IST, Greg Kroah-Hartman > wrote: > >This is the start of the stable review cycle for the 3.18.107 release. > >There are 24 patches in this series, all will be posted as a

Re: [PATCH 3.18 00/24] 3.18.107-stable review

On Sat, Apr 28, 2018 at 03:03:04AM +0530, Harsh Shandilya wrote: > On 27 April 2018 7:27:35 PM IST, Greg Kroah-Hartman > wrote: > >This is the start of the stable review cycle for the 3.18.107 release. > >There are 24 patches in this series, all will be posted as a response > >to this one. If

Re: [PATCH 3.18 00/24] 3.18.107-stable review

On Fri, Apr 27, 2018 at 12:12:32PM -0600, Shuah Khan wrote: > On 04/27/2018 07:57 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 3.18.107 release. > > There are 24 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: kernel-4.9.94 compile error: 'KMOD_DECOMP_LEN' undeclared

On Fri, Apr 27, 2018 at 10:28:27AM -0700, Randy Dunlap wrote: > [adding some Cc:] > > On 04/14/2018 02:41 AM, Teck Choon Giam wrote: > > Hi, > > > > Compile linux-4.9.94 will have error related to KMOD_DECOMP_LEN > > undeclared. Searching string related to KMOD_DECOMP_LEN in > > linux-4.9.94

Re: kernel-4.9.94 compile error: 'KMOD_DECOMP_LEN' undeclared

On Fri, Apr 27, 2018 at 10:28:27AM -0700, Randy Dunlap wrote: > [adding some Cc:] > > On 04/14/2018 02:41 AM, Teck Choon Giam wrote: > > Hi, > > > > Compile linux-4.9.94 will have error related to KMOD_DECOMP_LEN > > undeclared. Searching string related to KMOD_DECOMP_LEN in > > linux-4.9.94

Re: [PATCH v6 02/24] soc: qcom: Add APR bus driver

On Thu 26 Apr 02:45 PDT 2018, Srinivas Kandagatla wrote: > diff --git a/drivers/soc/qcom/apr.c b/drivers/soc/qcom/apr.c [..] > +int apr_send_pkt(struct apr_device *adev, void *buf) Sorry, but I think we have discussed this before? "buf" isn't some random buffer to be sent, it is a apr_hdr

Re: [PATCH v6 02/24] soc: qcom: Add APR bus driver

On Thu 26 Apr 02:45 PDT 2018, Srinivas Kandagatla wrote: > diff --git a/drivers/soc/qcom/apr.c b/drivers/soc/qcom/apr.c [..] > +int apr_send_pkt(struct apr_device *adev, void *buf) Sorry, but I think we have discussed this before? "buf" isn't some random buffer to be sent, it is a apr_hdr

Re: [PATCH v3 4/7] kprobes: Replace %p with other pointer types

On Sat, 28 Apr 2018 00:42:02 +0900 Masami Hiramatsu wrote: > > > +/* Caller must NOT call this in usual path. This is only for critical > > > case */ > > > void dump_kprobe(struct kprobe *kp) > > > { > > > - printk(KERN_WARNING "Dumping kprobe:\n"); > > > -

Re: [PATCH v3 4/7] kprobes: Replace %p with other pointer types

On Sat, 28 Apr 2018 00:42:02 +0900 Masami Hiramatsu wrote: > > > +/* Caller must NOT call this in usual path. This is only for critical > > > case */ > > > void dump_kprobe(struct kprobe *kp) > > > { > > > - printk(KERN_WARNING "Dumping kprobe:\n"); > > > - printk(KERN_WARNING "Name:

[PATCH] kselftests: fix grammar and non-ASCII space

From: Randy Dunlap This is a small cleanup to kselftest.rst: - Fix some language typos in the usage instructions. - Change one non-ASCII space to an ASCII space. Signed-off-by: Randy Dunlap --- Documentation/dev-tools/kselftest.rst | 12

[PATCH] kselftests: fix grammar and non-ASCII space

From: Randy Dunlap This is a small cleanup to kselftest.rst: - Fix some language typos in the usage instructions. - Change one non-ASCII space to an ASCII space. Signed-off-by: Randy Dunlap --- Documentation/dev-tools/kselftest.rst | 12 ++-- 1 file changed, 6 insertions(+), 6

[PATCH net-next] libcxgb,cxgb4: use __skb_put_zero to simplfy code

use helper __skb_put_zero to replace the pattern of __skb_put() && memset() Signed-off-by: YueHaibing --- drivers/net/ethernet/chelsio/cxgb4/cxgb4_filter.c | 3 +-- drivers/net/ethernet/chelsio/cxgb4/srq.c | 3 +--

[PATCH net-next] libcxgb,cxgb4: use __skb_put_zero to simplfy code

use helper __skb_put_zero to replace the pattern of __skb_put() && memset() Signed-off-by: YueHaibing --- drivers/net/ethernet/chelsio/cxgb4/cxgb4_filter.c | 3 +-- drivers/net/ethernet/chelsio/cxgb4/srq.c | 3 +-- drivers/net/ethernet/chelsio/libcxgb/libcxgb_cm.h | 15

Re: [PATCH 3.18 00/24] 3.18.107-stable review

On Fri, Apr 27, 2018 at 03:41:28PM -0400, Theodore Y. Ts'o wrote: > On Fri, Apr 27, 2018 at 03:57:35PM +0200, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 3.18.107 release. > > The kernel.org page currently lists 3.18 as EOL. I assume we released > an update

Re: [PATCH 3.18 00/24] 3.18.107-stable review

On Fri, Apr 27, 2018 at 03:41:28PM -0400, Theodore Y. Ts'o wrote: > On Fri, Apr 27, 2018 at 03:57:35PM +0200, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 3.18.107 release. > > The kernel.org page currently lists 3.18 as EOL. I assume we released > an update

[PATCH v2] staging: greybus: Use gpio_is_valid()

Replace the manual validity checks for the GPIO with the gpio_is_valid(). Signed-off-by: Arvind Yadav --- chnage in v2 : Returning invalid gpio as error instead of -ENODEV. drivers/staging/greybus/arche-platform.c | 6 +++--- 1 file changed, 3

[PATCH v2] staging: greybus: Use gpio_is_valid()

Replace the manual validity checks for the GPIO with the gpio_is_valid(). Signed-off-by: Arvind Yadav --- chnage in v2 : Returning invalid gpio as error instead of -ENODEV. drivers/staging/greybus/arche-platform.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff

Re: [greybus-dev] [PATCH] staging: greybus: Use gpio_is_valid()

On Friday 27 April 2018 06:32 PM, Alex Elder wrote: On 04/27/2018 07:50 AM, Arvind Yadav wrote: On Friday 27 April 2018 05:47 PM, Alex Elder wrote: On 04/27/2018 05:52 AM, Arvind Yadav wrote: Replace the manual validity checks for the GPIO with the gpio_is_valid(). I haven't looked

Re: [greybus-dev] [PATCH] staging: greybus: Use gpio_is_valid()

On Friday 27 April 2018 06:32 PM, Alex Elder wrote: On 04/27/2018 07:50 AM, Arvind Yadav wrote: On Friday 27 April 2018 05:47 PM, Alex Elder wrote: On 04/27/2018 05:52 AM, Arvind Yadav wrote: Replace the manual validity checks for the GPIO with the gpio_is_valid(). I haven't looked

Re: drivers/platform/x86/dell-smbios-wmi.c:66: undefined reference to `wmidev_evaluate_method'

On Fri, Apr 27, 2018 at 02:57:21PM -0700, Randy Dunlap wrote: > On 04/27/2018 11:01 AM, mario.limoncie...@dell.com wrote: ... > DELL_SMBIOS depends on ACPI_WMI so when ACPI_WMI=m, DELL_SMBIOS should never > =y. > Your DELL_LAPTOP Kconfig patch does fix this, I believe, because when >

Re: drivers/platform/x86/dell-smbios-wmi.c:66: undefined reference to `wmidev_evaluate_method'

On Fri, Apr 27, 2018 at 02:57:21PM -0700, Randy Dunlap wrote: > On 04/27/2018 11:01 AM, mario.limoncie...@dell.com wrote: ... > DELL_SMBIOS depends on ACPI_WMI so when ACPI_WMI=m, DELL_SMBIOS should never > =y. > Your DELL_LAPTOP Kconfig patch does fix this, I believe, because when >

Re: [PATCH] ARM: BCM5301X: Fix NAND ECC parameters for Linksys Panamera

On Fri, Apr 27, 2018 at 10:05 AM, Vivek Unune wrote: > On Wed, Apr 25, 2018 at 11:02:04AM +0200, Rafał Miłecki wrote: >> >> The easiest solution: ignore all these "error -74 (ECC error) while >> reading" errors (they may last for few minutes!). I believe UBI should >>

Re: [PATCH] ARM: BCM5301X: Fix NAND ECC parameters for Linksys Panamera

On Fri, Apr 27, 2018 at 10:05 AM, Vivek Unune wrote: > On Wed, Apr 25, 2018 at 11:02:04AM +0200, Rafał Miłecki wrote: >> >> The easiest solution: ignore all these "error -74 (ECC error) while >> reading" errors (they may last for few minutes!). I believe UBI should >> simply recreate all pages it

[Cubieboard-2] Booting up stuck at runlevel-2

Hi All. After a lot of hit-and-trials, I have managed to get some bootup. Unfortunately, not able to get a login-prompt. Following have been done : == u-boot == u-boot has been compiled using bleeding-edge mainline (ec5c4a8fd64a178a4d159917cda0aa176e5a9be5), via : * make

[Cubieboard-2] Booting up stuck at runlevel-2

Hi All. After a lot of hit-and-trials, I have managed to get some bootup. Unfortunately, not able to get a login-prompt. Following have been done : == u-boot == u-boot has been compiled using bleeding-edge mainline (ec5c4a8fd64a178a4d159917cda0aa176e5a9be5), via : * make

Re: [PATCH] mm: provide a fallback for PAGE_KERNEL_RO for architectures

On Fri, Apr 27, 2018 at 05:15:26PM -0700, Luis R. Rodriguez wrote: > Some architectures do not define PAGE_KERNEL_RO, best we can do > for them is to provide a fallback onto PAGE_KERNEL. Remove the > hack from the firmware loader and move it onto the asm-generic > header, and document while at it

Re: [PATCH] mm: provide a fallback for PAGE_KERNEL_RO for architectures

On Fri, Apr 27, 2018 at 05:15:26PM -0700, Luis R. Rodriguez wrote: > Some architectures do not define PAGE_KERNEL_RO, best we can do > for them is to provide a fallback onto PAGE_KERNEL. Remove the > hack from the firmware loader and move it onto the asm-generic > header, and document while at it

[PATCH 1/1] tg3: fix meaningless hw_stats reading after tg3_halt memset 0 hw_stats

Reading hw_stats will get the actual data after a sucessfull tg3_reset_hw, which actually after tg3_timer_start, so tg->hw_stats_flag is introduced to tell tg3_get_stats64 when hw_stats is ready to read, and it will be false after having done memset(tp->hw_stats, 0) in tg3_halt. Plus

[PATCH 1/1] tg3: fix meaningless hw_stats reading after tg3_halt memset 0 hw_stats

Reading hw_stats will get the actual data after a sucessfull tg3_reset_hw, which actually after tg3_timer_start, so tg->hw_stats_flag is introduced to tell tg3_get_stats64 when hw_stats is ready to read, and it will be false after having done memset(tp->hw_stats, 0) in tg3_halt. Plus

Re: [PATCH v1 2/4] mhi_bus: controller: MHI support for QCOM modems

Hi Sujeev, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.17-rc2 next-20180426] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v1 2/4] mhi_bus: controller: MHI support for QCOM modems

Hi Sujeev, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.17-rc2 next-20180426] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v4 6/7] ARM: dts: Add support for emtrion emCON-MX6 series

On Fri, Apr 27, 2018 at 03:24:41PM +0200, jan.tu...@emtrion.com wrote: > From: Jan Tuerk > > This patch adds support for the emtrion GmbH emCON-MX6 modules. > They are available with imx.6 Solo, Dual-Lite, Dual and Quad > equipped with Memory from 512MB to 2GB (configured

Re: [PATCH v4 6/7] ARM: dts: Add support for emtrion emCON-MX6 series

On Fri, Apr 27, 2018 at 03:24:41PM +0200, jan.tu...@emtrion.com wrote: > From: Jan Tuerk > > This patch adds support for the emtrion GmbH emCON-MX6 modules. > They are available with imx.6 Solo, Dual-Lite, Dual and Quad > equipped with Memory from 512MB to 2GB (configured by U-Boot). > > Our

Re: [PATCH v2] init: Fix false positives in W+X checking

On Fri, Apr 27, 2018 at 2:55 PM, Jeffrey Hugo wrote: > load_module() creates W+X mappings via __vmalloc_node_range() (from > layout_and_allocate()->move_module()->module_alloc()) by using > PAGE_KERNEL_EXEC. These mappings are later cleaned up via > "call_rcu_sched(>rcu,

Re: [PATCH v1 2/4] mhi_bus: controller: MHI support for QCOM modems

Hi Sujeev, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.17-rc2 next-20180426] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v2] init: Fix false positives in W+X checking

On Fri, Apr 27, 2018 at 2:55 PM, Jeffrey Hugo wrote: > load_module() creates W+X mappings via __vmalloc_node_range() (from > layout_and_allocate()->move_module()->module_alloc()) by using > PAGE_KERNEL_EXEC. These mappings are later cleaned up via > "call_rcu_sched(>rcu, do_free_init)" from

Re: [PATCH v1 2/4] mhi_bus: controller: MHI support for QCOM modems

Hi Sujeev, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.17-rc2 next-20180426] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: kselftest archives etc.

Hello! On 27 April 2018 at 19:17, Randy Dunlap wrote: [...] > so I looked for an archive of linux-kselft...@vger.kernel.org. > http://vger.kernel.org/vger-lists.html lists all mailing lists and > (some of) their archives, but none for linux-kselftest. For what it's

Re: kselftest archives etc.

Hello! On 27 April 2018 at 19:17, Randy Dunlap wrote: [...] > so I looked for an archive of linux-kselft...@vger.kernel.org. > http://vger.kernel.org/vger-lists.html lists all mailing lists and > (some of) their archives, but none for linux-kselftest. For what it's worth, as of last November

[PATCH v4 1/2] dma-mapping: move dma configuration to bus infrastructure

It is bus specific aspect to map a given device on the bus and relevant firmware description of its DMA configuration. So, this change introduces 'dma_configure' as bus callback giving flexibility to busses for implementing its own dma configuration function. The change eases the addition of new

Re: [PATCH v1 1/4] mhi_bus: core: Add support for MHI host interface

Hi Sujeev, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.17-rc2 next-20180426] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH v4 1/2] dma-mapping: move dma configuration to bus infrastructure

It is bus specific aspect to map a given device on the bus and relevant firmware description of its DMA configuration. So, this change introduces 'dma_configure' as bus callback giving flexibility to busses for implementing its own dma configuration function. The change eases the addition of new

Re: [PATCH v1 1/4] mhi_bus: core: Add support for MHI host interface

Hi Sujeev, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.17-rc2 next-20180426] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH v4 2/2] drivers: remove force dma flag from buses

With each bus implementing its own DMA configuration callback, there is no need for bus to explicitly have force_dma in its global structure. This patch modifies of_dma_configure API to accept an input parameter which specifies if implicit DMA configuration is required even when it is not

[PATCH v4 2/2] drivers: remove force dma flag from buses

With each bus implementing its own DMA configuration callback, there is no need for bus to explicitly have force_dma in its global structure. This patch modifies of_dma_configure API to accept an input parameter which specifies if implicit DMA configuration is required even when it is not

Re: [RFC v3 0/5] virtio: support packed ring

On 2018年04月27日 17:12, Tiwei Bie wrote: On Fri, Apr 27, 2018 at 02:17:51PM +0800, Jason Wang wrote: On 2018年04月27日 12:18, Michael S. Tsirkin wrote: On Fri, Apr 27, 2018 at 11:56:05AM +0800, Jason Wang wrote: On 2018年04月25日 13:15, Tiwei Bie wrote: Hello everyone, This RFC implements packed

Re: [RFC v3 0/5] virtio: support packed ring

On 2018年04月27日 17:12, Tiwei Bie wrote: On Fri, Apr 27, 2018 at 02:17:51PM +0800, Jason Wang wrote: On 2018年04月27日 12:18, Michael S. Tsirkin wrote: On Fri, Apr 27, 2018 at 11:56:05AM +0800, Jason Wang wrote: On 2018年04月25日 13:15, Tiwei Bie wrote: Hello everyone, This RFC implements packed

Re: [PATCH v2 2/2] usb: dwc3: support clocks and resets for DWC3 core

Hi Martin, 2018-04-24 2:44 GMT+09:00 Martin Blumenstingl : > Hello, > > On Thu, Apr 19, 2018 at 1:03 PM, Masahiro Yamada > wrote: >> Historically, the clocks and resets are handled on the glue layer >> side instead of the DWC3

Re: [PATCH v2 2/2] usb: dwc3: support clocks and resets for DWC3 core

Hi Martin, 2018-04-24 2:44 GMT+09:00 Martin Blumenstingl : > Hello, > > On Thu, Apr 19, 2018 at 1:03 PM, Masahiro Yamada > wrote: >> Historically, the clocks and resets are handled on the glue layer >> side instead of the DWC3 core. For simple cases, dwc3-of-simple.c >> takes care of arbitrary

RE: [PATCH v4 05/22] iommu: introduce iommu invalidate API function

> From: Jean-Philippe Brucker [mailto:jean-philippe.bruc...@arm.com] > Sent: Saturday, April 28, 2018 2:08 AM > > [...] > >> If this corresponds to QI_GRAN_ALL_ALL in patch 9, the comment should > >> be "Cache of all PASIDs"? Or maybe "all entries for all PASIDs"? Is it > >> different from

RE: [PATCH v4 05/22] iommu: introduce iommu invalidate API function

> From: Jean-Philippe Brucker [mailto:jean-philippe.bruc...@arm.com] > Sent: Saturday, April 28, 2018 2:08 AM > > [...] > >> If this corresponds to QI_GRAN_ALL_ALL in patch 9, the comment should > >> be "Cache of all PASIDs"? Or maybe "all entries for all PASIDs"? Is it > >> different from

Re: [PATCH v2] f2fs: fix to avoid race during access gc_thread pointer

On 04/27, Chao Yu wrote: > On 2018/4/27 10:04, Chao Yu wrote: > > On 2018/4/27 0:03, Jaegeuk Kim wrote: > >> On 04/24, Chao Yu wrote: > >>> Thread A Thread BThread C > >>> - f2fs_remount > >>> - stop_gc_thread > >>> - f2fs_sbi_store > >>>

Re: [PATCH v2] f2fs: fix to avoid race during access gc_thread pointer

On 04/27, Chao Yu wrote: > On 2018/4/27 10:04, Chao Yu wrote: > > On 2018/4/27 0:03, Jaegeuk Kim wrote: > >> On 04/24, Chao Yu wrote: > >>> Thread A Thread BThread C > >>> - f2fs_remount > >>> - stop_gc_thread > >>> - f2fs_sbi_store > >>>

Re: WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected

OK. Patch was sent to linux.git as 6c1e851c4edc13a4. #syz fix: random: fix possible sleeping allocation from irq context

Re: WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected

OK. Patch was sent to linux.git as 6c1e851c4edc13a4. #syz fix: random: fix possible sleeping allocation from irq context

Re: [PATCH v2] f2fs: fix to avoid race during access gc_thread pointer

On 04/27, Chao Yu wrote: > On 2018/4/27 0:03, Jaegeuk Kim wrote: > > On 04/24, Chao Yu wrote: > >> Thread A Thread BThread C > >> - f2fs_remount > >> - stop_gc_thread > >>- f2fs_sbi_store > >>

Re: [PATCH v2] f2fs: fix to avoid race during access gc_thread pointer

On 04/27, Chao Yu wrote: > On 2018/4/27 0:03, Jaegeuk Kim wrote: > > On 04/24, Chao Yu wrote: > >> Thread A Thread BThread C > >> - f2fs_remount > >> - stop_gc_thread > >>- f2fs_sbi_store > >>

Re: [PATCH v4 0/7] Add basic support for emtrion emCON-MX6 modules

On Fri, Apr 27, 2018 at 03:24:35PM +0200, jan.tu...@emtrion.com wrote: > From: Jan Tuerk > > Changes for v4: > - re-arrange the Patch-series to match the DT-submitting-patches > - Additional patch for the Documentation of the new DT-bindings > > [PATCH v4 1/7]

Re: [PATCH v4 0/7] Add basic support for emtrion emCON-MX6 modules

On Fri, Apr 27, 2018 at 03:24:35PM +0200, jan.tu...@emtrion.com wrote: > From: Jan Tuerk > > Changes for v4: > - re-arrange the Patch-series to match the DT-submitting-patches > - Additional patch for the Documentation of the new DT-bindings > > [PATCH v4 1/7] dt-bindings: display: Document

Re: [PATCH v2] f2fs: avoid stucking GC due to atomic write

On 04/27, Chao Yu wrote: > On 2018/4/26 23:54, Jaegeuk Kim wrote: > > On 04/24, Chao Yu wrote: > >> f2fs doesn't allow abuse on atomic write class interface, so except > >> limiting in-mem pages' total memory usage capacity, we need to limit > >> atomic-write usage as well when filesystem is

Re: [PATCH v2] f2fs: avoid stucking GC due to atomic write

On 04/27, Chao Yu wrote: > On 2018/4/26 23:54, Jaegeuk Kim wrote: > > On 04/24, Chao Yu wrote: > >> f2fs doesn't allow abuse on atomic write class interface, so except > >> limiting in-mem pages' total memory usage capacity, we need to limit > >> atomic-write usage as well when filesystem is

Re: general protection fault in fuse_ctl_remove_conn

>From 9f41081f8bd6762a6f629e5e23e6d07a62bba69c Mon Sep 17 00:00:00 2001 From: Tetsuo Handa Date: Sat, 28 Apr 2018 11:24:09 +0900 Subject: [PATCH] fuse: don't keep inode-less dentry at fuse_ctl_add_dentry(). syzbot is reporting NULL pointer dereference at

Re: general protection fault in fuse_ctl_remove_conn

>From 9f41081f8bd6762a6f629e5e23e6d07a62bba69c Mon Sep 17 00:00:00 2001 From: Tetsuo Handa Date: Sat, 28 Apr 2018 11:24:09 +0900 Subject: [PATCH] fuse: don't keep inode-less dentry at fuse_ctl_add_dentry(). syzbot is reporting NULL pointer dereference at fuse_ctl_remove_conn() [1]. Since

Re: [PATCH net] vhost: Use kzalloc() to allocate vhost_msg_node

On 2018年04月28日 09:51, Kevin Easton wrote: On Fri, Apr 27, 2018 at 09:07:56PM -0400, Kevin Easton wrote: On Fri, Apr 27, 2018 at 07:05:45PM +0300, Michael S. Tsirkin wrote: On Fri, Apr 27, 2018 at 11:45:02AM -0400, Kevin Easton wrote: The struct vhost_msg within struct vhost_msg_node is

Re: [PATCH net] vhost: Use kzalloc() to allocate vhost_msg_node

On 2018年04月28日 09:51, Kevin Easton wrote: On Fri, Apr 27, 2018 at 09:07:56PM -0400, Kevin Easton wrote: On Fri, Apr 27, 2018 at 07:05:45PM +0300, Michael S. Tsirkin wrote: On Fri, Apr 27, 2018 at 11:45:02AM -0400, Kevin Easton wrote: The struct vhost_msg within struct vhost_msg_node is

[PATCH v2 0/2] net: stmmac: dwmac-meson: 100M phy mode support for AXG SoC

Due to the dwmac glue layer register changed, we need to introduce a new compatible name for the Meson-AXG SoC to support for the RMII 100M ethernet PHY. Change since v1 at [1]: - implement set_phy_mode() for each SoC [1] https://lkml.kernel.org/r/20180426160508.29380-1-yixun@amlogic.com

[PATCH v2 1/2] dt-bindings: net: meson-dwmac: new compatible name for AXG SoC

We need to introduce a new compatible name for the Meson-AXG SoC in order to support the RMII 100M ethernet PHY, since the PRG_ETH0 register of the dwmac glue layer is changed from previous old SoC. Signed-off-by: Yixun Lan ---

  1   2   3   4   5   6   7   8   9   10   >