[PATCH 4.9 015/130] perf trace: Use the syscall raw_syscalls:sys_enter timestamp

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arnaldo Carvalho de Melo commit ecf1e2253ea79c6204f4d6a5e756e8fb4aed5a7e upstream. Instead of the one when another syscall takes place while another is being processed (in

[PATCH 4.9 015/130] perf trace: Use the syscall raw_syscalls:sys_enter timestamp

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arnaldo Carvalho de Melo commit ecf1e2253ea79c6204f4d6a5e756e8fb4aed5a7e upstream. Instead of the one when another syscall takes place while another is being processed (in another CPU, but we

[PATCH 4.4 36/42] ARM: ux500: fix prcmu_is_cpu_in_wfi() calculation

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit f0e8faa7a5e894b0fc99d24be1b18685a92ea466 upstream. This function clearly never worked and always returns true, as pointed out by gcc-7:

[PATCH 4.4 36/42] ARM: ux500: fix prcmu_is_cpu_in_wfi() calculation

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit f0e8faa7a5e894b0fc99d24be1b18685a92ea466 upstream. This function clearly never worked and always returns true, as pointed out by gcc-7: arch/arm/mach-ux500/pm.c: In

[PATCH 4.4 41/42] selftest/powerpc: Wrong PMC initialized in pmc56_overflow test

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Madhavan Srinivasan commit df21d2fa733035e4d414379960f94b2516b41296 upstream. Test uses PMC2 to count the event. But PMC1 is being initialized. Patch to fix it.

[PATCH 4.9 001/130] IB/core: Release allocated memory in cache setup failure

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Leon Romanovsky commit aa6aae38f7fb2c030f326a6dd10b58fff1851dfa upstream. The failure in ib_cache_setup_one function during ib_register_device will leave leaked allocated

[PATCH 4.9 011/130] IB/mlx4: Fix port query for 56Gb Ethernet links

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Saeed Mahameed commit 6fa26208206c406fa529cd73f7ae6bf4181e270b upstream. Report the correct speed in the port attributes when using a 56Gbps ethernet link. Without this

[PATCH 4.4 33/42] arm64/ptrace: Avoid uninitialised struct padding in fpr_set()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dave Martin commit aeb1f39d814b2e21e5e5706a48834bfd553d0059 upstream. This patch adds an explicit __reserved[] field to user_fpsimd_state to replace what was previously

[PATCH 4.9 010/130] IB/mlx4: Handle well-known-gid in mad_demux processing

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jack Morgenstein commit befcabcd530e4ffb6f016638f693b7d94986d2ba upstream. If OpenSM runs over a ConnectX-3, and there are ConnectX-4 or Connect-IB VFs active on the

[PATCH 4.9 011/130] IB/mlx4: Fix port query for 56Gb Ethernet links

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Saeed Mahameed commit 6fa26208206c406fa529cd73f7ae6bf4181e270b upstream. Report the correct speed in the port attributes when using a 56Gbps ethernet link. Without this change the field is

[PATCH 4.4 33/42] arm64/ptrace: Avoid uninitialised struct padding in fpr_set()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dave Martin commit aeb1f39d814b2e21e5e5706a48834bfd553d0059 upstream. This patch adds an explicit __reserved[] field to user_fpsimd_state to replace what was previously unnamed padding. This

[PATCH 4.9 010/130] IB/mlx4: Handle well-known-gid in mad_demux processing

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jack Morgenstein commit befcabcd530e4ffb6f016638f693b7d94986d2ba upstream. If OpenSM runs over a ConnectX-3, and there are ConnectX-4 or Connect-IB VFs active on the network, the OpenSM will

[PATCH 4.4 41/42] selftest/powerpc: Wrong PMC initialized in pmc56_overflow test

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Madhavan Srinivasan commit df21d2fa733035e4d414379960f94b2516b41296 upstream. Test uses PMC2 to count the event. But PMC1 is being initialized. Patch to fix it. Fixes: 3752e453f6ba

[PATCH 4.9 001/130] IB/core: Release allocated memory in cache setup failure

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Leon Romanovsky commit aa6aae38f7fb2c030f326a6dd10b58fff1851dfa upstream. The failure in ib_cache_setup_one function during ib_register_device will leave leaked allocated memory. Fixes:

[PATCH 4.4 39/42] [media] ite-cir: initialize use_demodulator before using it

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Nicolas Iooss commit 7ec03e60ef81c19b5d3a46dd070ee966774b860f upstream. Function ite_set_carrier_params() uses variable use_demodulator after having initialized it

[PATCH 4.9 017/130] perf trace: Check if MAP_32BIT is defined (again)

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Olsa commit 2bd42f3aaa53ebe78b9be6f898b7945dd61f9773 upstream. There might be systems where MAP_32BIT is not defined, like some some RHEL7 powerpc versions.

[PATCH 4.9 012/130] IB/mlx4: When no DMFS for IPoIB, dont allow NET_IF QPs

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eran Ben Elisha commit 1f22e454df2eb99ba6b7ace3f594f6805cdf5cbc upstream. According to the firmware spec, FLOW_STEERING_IB_UC_QP_RANGE command is supported only if

[PATCH 4.4 39/42] [media] ite-cir: initialize use_demodulator before using it

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Nicolas Iooss commit 7ec03e60ef81c19b5d3a46dd070ee966774b860f upstream. Function ite_set_carrier_params() uses variable use_demodulator after having initialized it to false in some if

[PATCH 4.9 017/130] perf trace: Check if MAP_32BIT is defined (again)

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Olsa commit 2bd42f3aaa53ebe78b9be6f898b7945dd61f9773 upstream. There might be systems where MAP_32BIT is not defined, like some some RHEL7 powerpc versions. Signed-off-by: Jiri Olsa Cc:

[PATCH 4.9 012/130] IB/mlx4: When no DMFS for IPoIB, dont allow NET_IF QPs

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eran Ben Elisha commit 1f22e454df2eb99ba6b7ace3f594f6805cdf5cbc upstream. According to the firmware spec, FLOW_STEERING_IB_UC_QP_RANGE command is supported only if dmfs_ipoib bit is set. If

[PATCH 4.4 06/42] IB/mlx4: When no DMFS for IPoIB, dont allow NET_IF QPs

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Eran Ben Elisha commit 1f22e454df2eb99ba6b7ace3f594f6805cdf5cbc upstream. According to the firmware spec, FLOW_STEERING_IB_UC_QP_RANGE command is supported only if

[PATCH 4.4 04/42] IB/mlx4: Fix out-of-range array index in destroy qp flow

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jack Morgenstein commit c482af646d0809a8d5e1b7f4398cce3592589b98 upstream. For non-special QPs, the port value becomes non-zero only at the RESET-to-INIT transition.

[PATCH 4.4 06/42] IB/mlx4: When no DMFS for IPoIB, dont allow NET_IF QPs

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Eran Ben Elisha commit 1f22e454df2eb99ba6b7ace3f594f6805cdf5cbc upstream. According to the firmware spec, FLOW_STEERING_IB_UC_QP_RANGE command is supported only if dmfs_ipoib bit is set. If

[PATCH 4.4 04/42] IB/mlx4: Fix out-of-range array index in destroy qp flow

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jack Morgenstein commit c482af646d0809a8d5e1b7f4398cce3592589b98 upstream. For non-special QPs, the port value becomes non-zero only at the RESET-to-INIT transition. If the QP has not

[PATCH 4.4 07/42] IB/IPoIB: Remove cant use GFP_NOIO warning

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Kamal Heib commit 0b59970e7d96edcb3c7f651d9d48e1a59af3c3b0 upstream. Remove the warning print of "can't use of GFP_NOIO" to avoid prints in each QP creation when devices

[PATCH 4.4 07/42] IB/IPoIB: Remove cant use GFP_NOIO warning

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Kamal Heib commit 0b59970e7d96edcb3c7f651d9d48e1a59af3c3b0 upstream. Remove the warning print of "can't use of GFP_NOIO" to avoid prints in each QP creation when devices aren't supporting

[PATCH 4.4 26/42] svcrdma: avoid duplicate dma unmapping during error recovery

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sriharsha Basavapatna commit ce1ca7d2d140a1f4aaffd297ac487f246963dd2f upstream. In rdma_read_chunk_frmr() when ib_post_send() fails, the error code path

[PATCH 4.4 30/42] arm64/ptrace: Preserve previous registers for short regset write

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dave Martin commit 9a17b876b573441bfb3387ad55d98bf7184daf9d upstream. Ensure that if userspace supplies insufficient data to PTRACE_SETREGSET to fill all the registers,

[PATCH 4.4 26/42] svcrdma: avoid duplicate dma unmapping during error recovery

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sriharsha Basavapatna commit ce1ca7d2d140a1f4aaffd297ac487f246963dd2f upstream. In rdma_read_chunk_frmr() when ib_post_send() fails, the error code path invokes ib_dma_unmap_sg() to unmap the

[PATCH 4.4 30/42] arm64/ptrace: Preserve previous registers for short regset write

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dave Martin commit 9a17b876b573441bfb3387ad55d98bf7184daf9d upstream. Ensure that if userspace supplies insufficient data to PTRACE_SETREGSET to fill all the registers, the thread's old

[PATCH 4.4 20/42] ieee802154: atusb: do not use the stack for buffers to make them DMA able

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Stefan Schmidt commit 05a974efa4bdf6e2a150e3f27dc6fcf0a9ad5655 upstream. >From 4.9 we should really avoid using the stack here as this will not be DMA able on various

[PATCH 4.4 18/42] HID: corsair: fix control-transfer error handling

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 7a546af50eb78ab99840903083231eb635c8a566 upstream. Make sure to check for short control transfers in order to avoid parsing uninitialised buffer data and

[PATCH 4.4 18/42] HID: corsair: fix control-transfer error handling

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 7a546af50eb78ab99840903083231eb635c8a566 upstream. Make sure to check for short control transfers in order to avoid parsing uninitialised buffer data and leaking it to user

[PATCH 4.4 20/42] ieee802154: atusb: do not use the stack for buffers to make them DMA able

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Stefan Schmidt commit 05a974efa4bdf6e2a150e3f27dc6fcf0a9ad5655 upstream. >From 4.9 we should really avoid using the stack here as this will not be DMA able on various platforms. This changes

[PATCH 4.4 12/42] tmpfs: clear S_ISGID when setting posix ACLs

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Gu Zheng commit 497de07d89c1410d76a15bec2bb41f24a2a89f31 upstream. This change was missed the tmpfs modification in In CVE-2016-7097 commit 073931017b49 ("posix_acl: Clear

[PATCH 4.4 01/42] ftrace/x86: Set ftrace_stub to weak to prevent gcc from using short jumps to it

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Steven Rostedt commit 8329e818f14926a6040df86b2668568bde342ebf upstream. Matt Fleming reported seeing crashes when enabling and disabling function profiling which uses

[PATCH 4.4 12/42] tmpfs: clear S_ISGID when setting posix ACLs

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Gu Zheng commit 497de07d89c1410d76a15bec2bb41f24a2a89f31 upstream. This change was missed the tmpfs modification in In CVE-2016-7097 commit 073931017b49 ("posix_acl: Clear SGID bit when

[PATCH 4.4 01/42] ftrace/x86: Set ftrace_stub to weak to prevent gcc from using short jumps to it

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Steven Rostedt commit 8329e818f14926a6040df86b2668568bde342ebf upstream. Matt Fleming reported seeing crashes when enabling and disabling function profiling which uses function graph tracer.

[PATCH 4.4 13/42] x86/PCI: Ignore _CRS on Supermicro X8DTH-i/6/iF/6F

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Bjorn Helgaas commit 89e9f7bcd8744ea25fcf0ac671b8d72c10d7d790 upstream. Martin reported that the Supermicro X8DTH-i/6/iF/6F advertises incorrect host bridge windows via

[PATCH 4.4 11/42] ARM: dts: imx31: fix AVIC base address

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vladimir Zapolskiy commit af92305e567b7f4c9cf48b9e46c1f48ec9ffb1fb upstream. On i.MX31 AVIC interrupt controller base address is at 0x6800. The problem was

[PATCH 4.4 17/42] HID: corsair: fix DMA buffers on stack

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 6d104af38b570d37aa32a5803b04c354f8ed513d upstream. Not all platforms support DMA to the stack, and specifically since v4.9 this is no longer supported on

[PATCH 4.4 13/42] x86/PCI: Ignore _CRS on Supermicro X8DTH-i/6/iF/6F

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Bjorn Helgaas commit 89e9f7bcd8744ea25fcf0ac671b8d72c10d7d790 upstream. Martin reported that the Supermicro X8DTH-i/6/iF/6F advertises incorrect host bridge windows via _CRS: pci_root

[PATCH 4.4 11/42] ARM: dts: imx31: fix AVIC base address

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vladimir Zapolskiy commit af92305e567b7f4c9cf48b9e46c1f48ec9ffb1fb upstream. On i.MX31 AVIC interrupt controller base address is at 0x6800. The problem was shadowed by the AVIC driver,

[PATCH 4.4 17/42] HID: corsair: fix DMA buffers on stack

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 6d104af38b570d37aa32a5803b04c354f8ed513d upstream. Not all platforms support DMA to the stack, and specifically since v4.9 this is no longer supported on x86 with

Re: [PATCH] i2c: Fix error print when address is invalid

On Mon, Jan 23, 2017 at 06:24:24PM -0800, Stephen Boyd wrote: > When the address is invalid, we print out the address that's > in info.addr, but that member of info hasn't been assigned yet. > It's assigned in the line after we check the address. This causes > the print to show something like > >

Re: [PATCH] i2c: Fix error print when address is invalid

On Mon, Jan 23, 2017 at 06:24:24PM -0800, Stephen Boyd wrote: > When the address is invalid, we print out the address that's > in info.addr, but that member of info hasn't been assigned yet. > It's assigned in the line after we check the address. This causes > the print to show something like > >

[PATCH] netfilter: nf_ct_helper: warn when not applying default helper assignment (was Re: [RFC PATCH 0/2] restore original default of nf_conntrack_helper sysctl)

On Mon, 23 Jan 2017, Linus Torvalds wrote: > For all I know, there may be some security reason why we really don't > want the automatic helpers, even if they can be convenient. > > Also, you can just enable them with a kernel command line or a sysctl, > so it's not like you can't get the old

[PATCH] netfilter: nf_ct_helper: warn when not applying default helper assignment (was Re: [RFC PATCH 0/2] restore original default of nf_conntrack_helper sysctl)

On Mon, 23 Jan 2017, Linus Torvalds wrote: > For all I know, there may be some security reason why we really don't > want the automatic helpers, even if they can be convenient. > > Also, you can just enable them with a kernel command line or a sysctl, > so it's not like you can't get the old

[PATCH RFC 1/3] mm/hugetlb: split alloc_fresh_huge_page_node into fast and slow path

This patch split alloc_fresh_huge_page_node into 2 parts: - fast path without __GFP_REPEAT flag - slow path with __GFP_REPEAT flag Thus, if there is a server with uneven numa memory layout: available: 7 nodes (0-6) node 0 cpus: 0 1 2 3 4 5 6 7 node 0 size: 6603 MB node 0 free: 91 MB node 1 cpus:

[PATCH RFC 1/3] mm/hugetlb: split alloc_fresh_huge_page_node into fast and slow path

This patch split alloc_fresh_huge_page_node into 2 parts: - fast path without __GFP_REPEAT flag - slow path with __GFP_REPEAT flag Thus, if there is a server with uneven numa memory layout: available: 7 nodes (0-6) node 0 cpus: 0 1 2 3 4 5 6 7 node 0 size: 6603 MB node 0 free: 91 MB node 1 cpus:

[PATCH RFC 2/3] mm, vmscan: limit kswapd loop if no progress is made

Currently there is no hard limitation for kswapd retry times if no progress is made. Then kswapd will take 100% for a long time. In my test, I tried to allocate 4000 hugepages by: echo 4000 > /proc/sys/vm/nr_hugepages Then,kswapd will take 100% cpu for a long time. The numa layout is:

[PATCH RFC 2/3] mm, vmscan: limit kswapd loop if no progress is made

Currently there is no hard limitation for kswapd retry times if no progress is made. Then kswapd will take 100% for a long time. In my test, I tried to allocate 4000 hugepages by: echo 4000 > /proc/sys/vm/nr_hugepages Then,kswapd will take 100% cpu for a long time. The numa layout is:

[PATCH RFC 3/3] mm, vmscan: correct prepare_kswapd_sleep return value

When there is no reclaimable pages in the zone, even the zone is not balanced, we let kswapd go sleeping. That is prepare_kswapd_sleep will return true in this case. Signed-off-by: Jia He --- mm/vmscan.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git

[PATCH RFC 0/3] optimize kswapd when it does reclaim for hugepage

If there is a server with uneven numa memory layout: available: 7 nodes (0-6) node 0 cpus: 0 1 2 3 4 5 6 7 node 0 size: 6603 MB node 0 free: 91 MB node 1 cpus: node 1 size: 12527 MB node 1 free: 157 MB node 2 cpus: node 2 size: 15087 MB node 2 free: 189 MB node 3 cpus: node 3 size: 16111 MB node 3

[PATCH RFC 0/3] optimize kswapd when it does reclaim for hugepage

If there is a server with uneven numa memory layout: available: 7 nodes (0-6) node 0 cpus: 0 1 2 3 4 5 6 7 node 0 size: 6603 MB node 0 free: 91 MB node 1 cpus: node 1 size: 12527 MB node 1 free: 157 MB node 2 cpus: node 2 size: 15087 MB node 2 free: 189 MB node 3 cpus: node 3 size: 16111 MB node 3

[PATCH RFC 3/3] mm, vmscan: correct prepare_kswapd_sleep return value

When there is no reclaimable pages in the zone, even the zone is not balanced, we let kswapd go sleeping. That is prepare_kswapd_sleep will return true in this case. Signed-off-by: Jia He --- mm/vmscan.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/mm/vmscan.c

Re: [PATCH] USB: Add quirk for WORLDE easykey.25 MIDI keyboard

On Tue, Jan 24, 2017 at 8:32 AM, Oliver Neukum wrote: > Am Montag, den 23.01.2017, 19:36 +0100 schrieb Lukáš Lalinský: >> I have uploaded both captures here - >> https://gist.github.com/lalinsky/83148a827d5cd43e79e377d8e1b5ed0d > > Indeed it is does not set a configuration.

Re: [PATCH] USB: Add quirk for WORLDE easykey.25 MIDI keyboard

On Tue, Jan 24, 2017 at 8:32 AM, Oliver Neukum wrote: > Am Montag, den 23.01.2017, 19:36 +0100 schrieb Lukáš Lalinský: >> I have uploaded both captures here - >> https://gist.github.com/lalinsky/83148a827d5cd43e79e377d8e1b5ed0d > > Indeed it is does not set a configuration. Either the capture >

Re: v4.10-rc4 to v4.10-rc5: battery regression on Nokia N900

On Tue 2017-01-24 15:06:39, Zhang Rui wrote: > On Mon, Jan 23, 2017 at 03:49:12PM -0800, Guenter Roeck wrote: > > On Tue, Jan 24, 2017 at 12:26:54AM +0100, Pavel Machek wrote: > > > Hi! > > > > > > > > >I'll try to revert it on the top of v4.10-rc5 now... and yes, it > > > > > >fixes > > > > >

Re: v4.10-rc4 to v4.10-rc5: battery regression on Nokia N900

On Tue 2017-01-24 15:06:39, Zhang Rui wrote: > On Mon, Jan 23, 2017 at 03:49:12PM -0800, Guenter Roeck wrote: > > On Tue, Jan 24, 2017 at 12:26:54AM +0100, Pavel Machek wrote: > > > Hi! > > > > > > > > >I'll try to revert it on the top of v4.10-rc5 now... and yes, it > > > > > >fixes > > > > >

Re: v4.10-rc4 to v4.10-rc5: battery regression on Nokia N900

Hi! > > > > >I'll try to revert it on the top of v4.10-rc5 now... and yes, it fixes > > > > >the issue. > > > > > > > > > >Any idea what went wrong and how to fix that? > > > > > > > > > >Anyway as we are at -rc5 and this is warning fix that caused a > > > > >regression on different hardware...

Re: v4.10-rc4 to v4.10-rc5: battery regression on Nokia N900

Hi! > > > > >I'll try to revert it on the top of v4.10-rc5 now... and yes, it fixes > > > > >the issue. > > > > > > > > > >Any idea what went wrong and how to fix that? > > > > > > > > > >Anyway as we are at -rc5 and this is warning fix that caused a > > > > >regression on different hardware...

Re: [PATCH] USB: Add quirk for WORLDE easykey.25 MIDI keyboard

Am Montag, den 23.01.2017, 19:36 +0100 schrieb Lukáš Lalinský: > On Sat, Jan 21, 2017 at 10:08 AM, Greg Kroah-Hartman > wrote: > > > > Always use scripts/get_maintainer.pl to determine who to send > > patches > > to, and what mailing list.  You forgot linux-usb@vger,

Re: [PATCH] USB: Add quirk for WORLDE easykey.25 MIDI keyboard

Am Montag, den 23.01.2017, 19:36 +0100 schrieb Lukáš Lalinský: > On Sat, Jan 21, 2017 at 10:08 AM, Greg Kroah-Hartman > wrote: > > > > Always use scripts/get_maintainer.pl to determine who to send > > patches > > to, and what mailing list.  You forgot linux-usb@vger, which I've > > now > >

Re: [PATCH 6/9] power_supply: wm97xx_battery: use power_supply_get_drvdata

Kevin Hilman writes: > Hello, > > On Wed, Oct 26, 2016 at 12:41 PM, Robert Jarzmik > wrote: >> As the power supply framework provides a way to store and retrieve >> private supply data, use it. >> >> In the process, change the platform data for

Re: [PATCH 6/9] power_supply: wm97xx_battery: use power_supply_get_drvdata

Kevin Hilman writes: > Hello, > > On Wed, Oct 26, 2016 at 12:41 PM, Robert Jarzmik > wrote: >> As the power supply framework provides a way to store and retrieve >> private supply data, use it. >> >> In the process, change the platform data for wm97xx_battery from a >> container of a single

Re: [PATCH] mmc: s3cmci: include linux/interrupt.h for tasklet_struct

On 20 January 2017 at 21:08, Arnd Bergmann wrote: > I got this new build error on today's linux-next > > drivers/mmc/host/s3cmci.h:69:24: error: field 'pio_tasklet' has incomplete > type > struct tasklet_struct pio_tasklet; > drivers/mmc/host/s3cmci.c: In function

Re: [PATCH] mmc: s3cmci: include linux/interrupt.h for tasklet_struct

On 20 January 2017 at 21:08, Arnd Bergmann wrote: > I got this new build error on today's linux-next > > drivers/mmc/host/s3cmci.h:69:24: error: field 'pio_tasklet' has incomplete > type > struct tasklet_struct pio_tasklet; > drivers/mmc/host/s3cmci.c: In function 's3cmci_enable_irq': >

Re: [PATCH] Bluetooth: hidp: might sleep error in hidp_session_thread

Hi brian, On 01/24/2017 10:31 AM, Brian Norris wrote: Hi Jeffy, On Fri, Jan 20, 2017 at 09:52:08PM +0800, Jeffy Chen wrote: [ 39.044329] do not call blocking ops when !TASK_RUNNING; state=1 set at [] hidp_session_thread+0x110/0x568 [hidp] ... [ 40.159664] Call trace: [ 40.162122] []

Re: [PATCH] Bluetooth: hidp: might sleep error in hidp_session_thread

Hi brian, On 01/24/2017 10:31 AM, Brian Norris wrote: Hi Jeffy, On Fri, Jan 20, 2017 at 09:52:08PM +0800, Jeffy Chen wrote: [ 39.044329] do not call blocking ops when !TASK_RUNNING; state=1 set at [] hidp_session_thread+0x110/0x568 [hidp] ... [ 40.159664] Call trace: [ 40.162122] []

Re: v4.10-rc4 to v4.10-rc5: battery regression on Nokia N900

On Mon, Jan 23, 2017 at 03:49:12PM -0800, Guenter Roeck wrote: > On Tue, Jan 24, 2017 at 12:26:54AM +0100, Pavel Machek wrote: > > Hi! > > > > > > >I'll try to revert it on the top of v4.10-rc5 now... and yes, it fixes > > > > >the issue. > > > > > > > > > >Any idea what went wrong and how to fix

Re: v4.10-rc4 to v4.10-rc5: battery regression on Nokia N900

On Mon, Jan 23, 2017 at 03:49:12PM -0800, Guenter Roeck wrote: > On Tue, Jan 24, 2017 at 12:26:54AM +0100, Pavel Machek wrote: > > Hi! > > > > > > >I'll try to revert it on the top of v4.10-rc5 now... and yes, it fixes > > > > >the issue. > > > > > > > > > >Any idea what went wrong and how to fix

Re: [PATCH] kernel-doc: Handle returning pointers to pointers

Am 23.01.2017 um 16:24 schrieb Jonathan Corbet : > On Mon, 23 Jan 2017 15:14:51 + > Matthew Wilcox wrote: > >>> I maintain my own stack of "linuxdoc" with a python version >>> of the kernel-doc script (hosted on github). It uses the same >>> regexes

Re: [PATCH] kernel-doc: Handle returning pointers to pointers

Am 23.01.2017 um 16:24 schrieb Jonathan Corbet : > On Mon, 23 Jan 2017 15:14:51 + > Matthew Wilcox wrote: > >>> I maintain my own stack of "linuxdoc" with a python version >>> of the kernel-doc script (hosted on github). It uses the same >>> regexes as the perl version (using a python

Re: [PATCH v5 0/2] perf probe: add sdt probes arguments into the uprobe cmd string

On Wednesday 14 December 2016 01:06 PM, Ingo Molnar wrote: > * Alexis Berlemont wrote: > >> Hi Masami, >> >> Many thanks for your mail. >> >> Here is another patch set which tries to fix the points you mentioned: >> >> * Skip the arguments containing a constant

Re: [PATCH v5 0/2] perf probe: add sdt probes arguments into the uprobe cmd string

On Wednesday 14 December 2016 01:06 PM, Ingo Molnar wrote: > * Alexis Berlemont wrote: > >> Hi Masami, >> >> Many thanks for your mail. >> >> Here is another patch set which tries to fix the points you mentioned: >> >> * Skip the arguments containing a constant ($123); >> * Review the code in

[PATCH] Drivers: hv: vmbus: finally fix hv_need_to_signal_on_read()

Commit a389fcfd2cb5 ("Drivers: hv: vmbus: Fix signaling logic in hv_need_to_signal_on_read()") added the proper mb(), but removed the test "prev_write_sz < pending_sz" when making the signal decision. As a result, the guest can signal the host unnecessarily, and then the host can throttle the

[PATCH] Drivers: hv: vmbus: finally fix hv_need_to_signal_on_read()

Commit a389fcfd2cb5 ("Drivers: hv: vmbus: Fix signaling logic in hv_need_to_signal_on_read()") added the proper mb(), but removed the test "prev_write_sz < pending_sz" when making the signal decision. As a result, the guest can signal the host unnecessarily, and then the host can throttle the

Re: [patch] samples/bpf: silence shift wrapping warning

On Mon, Jan 23, 2017 at 5:27 AM, Arnaldo Carvalho de Melo wrote: > Em Sun, Jan 22, 2017 at 02:51:25PM -0800, Alexei Starovoitov escreveu: >> On Sat, Jan 21, 2017 at 07:51:43AM +0300, Dan Carpenter wrote: >> > max_key is a value in the 0-63 range, so on 32 bit systems the

Re: [patch] samples/bpf: silence shift wrapping warning

On Mon, Jan 23, 2017 at 5:27 AM, Arnaldo Carvalho de Melo wrote: > Em Sun, Jan 22, 2017 at 02:51:25PM -0800, Alexei Starovoitov escreveu: >> On Sat, Jan 21, 2017 at 07:51:43AM +0300, Dan Carpenter wrote: >> > max_key is a value in the 0-63 range, so on 32 bit systems the shift >> > could wrap. >>

Re: [PATCH v3 1/3] of: Support parsing phandle argument lists through a nexus node

Hi Stephen, Sorry I did not get to v1 and v2 in a timely manner. On 01/23/17 12:48, Stephen Boyd wrote: > Platforms like 96boards have a standardized connector/expansion > slot that exposes signals like GPIOs to expansion boards in an > SoC agnostic way. We'd like the DT overlays for the

Re: [PATCH v3 1/3] of: Support parsing phandle argument lists through a nexus node

Hi Stephen, Sorry I did not get to v1 and v2 in a timely manner. On 01/23/17 12:48, Stephen Boyd wrote: > Platforms like 96boards have a standardized connector/expansion > slot that exposes signals like GPIOs to expansion boards in an > SoC agnostic way. We'd like the DT overlays for the

Re: [GIT PULL] Immutable branch between MFD, ARM, IIO and PWM due for the v4.10 merge window

Hi Lee, On Mon, Jan 23, 2017 at 4:12 AM, Lee Jones wrote: > Arm, IIO and PWM Maintainers, > > Enjoy! > > The following changes since commit 7ce7d89f48834cefece7804d38fc5d85382edf77: > > Linux 4.10-rc1 (2016-12-25 16:13:08 -0800) > > are available in the git repository at:

Re: [GIT PULL] Immutable branch between MFD, ARM, IIO and PWM due for the v4.10 merge window

Hi Lee, On Mon, Jan 23, 2017 at 4:12 AM, Lee Jones wrote: > Arm, IIO and PWM Maintainers, > > Enjoy! > > The following changes since commit 7ce7d89f48834cefece7804d38fc5d85382edf77: > > Linux 4.10-rc1 (2016-12-25 16:13:08 -0800) > > are available in the git repository at: > >

[PATCH V6 1/5] LIB: Indirect ISA/LPC port IO introduced

Low-pin-count interface is integrated into some SoCs. The accesses to those peripherals under LPC make use of I/O ports rather than the memory mapped I/O. To drive these devices, this patch introduces a method named indirect-IO. In this method the in/out() accessor in include/asm-generic/io.h

[PATCH V6 3/5] OF: Add missing I/O range exception for indirect-IO devices

There are some special ISA/LPC devices that work on a specific I/O range where it is not correct to specify a 'ranges' property in DTS parent node as cpu addresses translated from DTS node are only for memory space on some architectures, such as Arm64. Without the parent 'ranges' property, current

[PATCH V6 3/5] OF: Add missing I/O range exception for indirect-IO devices

There are some special ISA/LPC devices that work on a specific I/O range where it is not correct to specify a 'ranges' property in DTS parent node as cpu addresses translated from DTS node are only for memory space on some architectures, such as Arm64. Without the parent 'ranges' property, current

[PATCH V6 1/5] LIB: Indirect ISA/LPC port IO introduced

Low-pin-count interface is integrated into some SoCs. The accesses to those peripherals under LPC make use of I/O ports rather than the memory mapped I/O. To drive these devices, this patch introduces a method named indirect-IO. In this method the in/out() accessor in include/asm-generic/io.h

[PATCH V6 0/5] LPC: legacy ISA I/O support

This patch supports the IPMI-bt device attached to the Low-Pin-Count interface implemented on Hisilicon Hip06/Hip07 SoC. --- | LPC host| | | --- |

[PATCH V6 0/5] LPC: legacy ISA I/O support

This patch supports the IPMI-bt device attached to the Low-Pin-Count interface implemented on Hisilicon Hip06/Hip07 SoC. --- | LPC host| | | --- |

[PATCH V6 2/5] PCI: Adapt pci_register_io_range() for indirect-IO and PCI I/O translation

After indirect-IO is introduced, system must can assigned indirect-IO devices with logical I/O ranges which are different from those for PCI I/O devices. Otherwise, I/O accessors can't identify whether the I/O port is for memory mapped I/O or indirect-IO. As current helper,

[PATCH V6 4/5] LPC: Support the device-tree LPC host on Hip06/Hip07

The low-pin-count(LPC) interface of Hip06/Hip07 accesses the peripherals in I/O port addresses. This patch implements the LPC host controller driver which perform the I/O operations on the underlying hardware. We don't want to touch those existing peripherals' driver, such as ipmi-bt. So this

[PATCH V5 5/5] LPC: Add the ACPI LPC support

The patch update the _CRS of LPC children with the system logical I/O resource after the translation from LPC-local I/O. Then the ACPI platform device enumeration for LPC can apply the right I/O resource to request the system I/O space. Signed-off-by: zhichang.yuan

[PATCH V6 2/5] PCI: Adapt pci_register_io_range() for indirect-IO and PCI I/O translation

After indirect-IO is introduced, system must can assigned indirect-IO devices with logical I/O ranges which are different from those for PCI I/O devices. Otherwise, I/O accessors can't identify whether the I/O port is for memory mapped I/O or indirect-IO. As current helper,

[PATCH V6 4/5] LPC: Support the device-tree LPC host on Hip06/Hip07

The low-pin-count(LPC) interface of Hip06/Hip07 accesses the peripherals in I/O port addresses. This patch implements the LPC host controller driver which perform the I/O operations on the underlying hardware. We don't want to touch those existing peripherals' driver, such as ipmi-bt. So this

[PATCH V5 5/5] LPC: Add the ACPI LPC support

The patch update the _CRS of LPC children with the system logical I/O resource after the translation from LPC-local I/O. Then the ACPI platform device enumeration for LPC can apply the right I/O resource to request the system I/O space. Signed-off-by: zhichang.yuan --- drivers/bus/hisi_lpc.c |

Re: [PATCH 1/3] PM / devfreq: Fix available_governor sysfs

On 2017년 01월 24일 12:51, MyungJoo Ham wrote: >> The devfreq using passive governor is not able to change the governor. >> So, the user can not change the governor through 'available_governor' sysfs >> entry. Also, the devfreq which don't use the passive governor is not able to >> change to

Re: [PATCH 1/3] PM / devfreq: Fix available_governor sysfs

On 2017년 01월 24일 12:51, MyungJoo Ham wrote: >> The devfreq using passive governor is not able to change the governor. >> So, the user can not change the governor through 'available_governor' sysfs >> entry. Also, the devfreq which don't use the passive governor is not able to >> change to

Re: [PATCH] drm: bridge: dw-hdmi: fix building without CONFIG_OF

On 01/23/2017 05:50 PM, Arnd Bergmann wrote: The of_node member in struct drm_bridge is hidden when CONFIG_OF is disabled, causing a build error: drivers/gpu/drm/bridge/dw-hdmi.c: In function '__dw_hdmi_probe': drivers/gpu/drm/bridge/dw-hdmi.c:2063:14: error: 'struct drm_bridge' has no

Re: [PATCH] drm: bridge: dw-hdmi: fix building without CONFIG_OF

On 01/23/2017 05:50 PM, Arnd Bergmann wrote: The of_node member in struct drm_bridge is hidden when CONFIG_OF is disabled, causing a build error: drivers/gpu/drm/bridge/dw-hdmi.c: In function '__dw_hdmi_probe': drivers/gpu/drm/bridge/dw-hdmi.c:2063:14: error: 'struct drm_bridge' has no

  1   2   3   4   5   6   7   8   9   10   >