[PATCH bpf-next v7 2/5] libbpf: add function to setup XDP

Most of the code is taken from set_link_xdp_fd() in bpf_load.c and slightly modified to be library compliant. Signed-off-by: Eric Leblond Acked-by: Alexei Starovoitov --- tools/lib/bpf/bpf.c| 127 +

[PATCH bpf-next v7 5/5] samples/bpf: use bpf_set_link_xdp_fd

Use bpf_set_link_xdp_fd instead of set_link_xdp_fd to remove some code duplication and benefit of netlink ext ack errors message. Signed-off-by: Eric Leblond --- samples/bpf/bpf_load.c | 102 samples/bpf/bpf_load.h |

[PATCH bpf-next v7 2/5] libbpf: add function to setup XDP

Most of the code is taken from set_link_xdp_fd() in bpf_load.c and slightly modified to be library compliant. Signed-off-by: Eric Leblond Acked-by: Alexei Starovoitov --- tools/lib/bpf/bpf.c| 127 + tools/lib/bpf/libbpf.c | 2 +

[PATCH bpf-next v7 5/5] samples/bpf: use bpf_set_link_xdp_fd

Use bpf_set_link_xdp_fd instead of set_link_xdp_fd to remove some code duplication and benefit of netlink ext ack errors message. Signed-off-by: Eric Leblond --- samples/bpf/bpf_load.c | 102 samples/bpf/bpf_load.h | 2 +-

Re: [PATCH 10/10] kill kernel_sock_ioctl()

On Wed, Jan 24, 2018 at 03:52:44PM -0500, David Miller wrote: > > Al this series looks fine to me, want me to toss it into net-next? Do you want them reposted (with updated commit messages), or would you prefer a pull request (with or without rebase to current tip of net-next)?

Re: [PATCH 10/10] kill kernel_sock_ioctl()

On Wed, Jan 24, 2018 at 03:52:44PM -0500, David Miller wrote: > > Al this series looks fine to me, want me to toss it into net-next? Do you want them reposted (with updated commit messages), or would you prefer a pull request (with or without rebase to current tip of net-next)?

[PATCH] mailbox: Avoid NULL dereference in mbox_chan_received_data

If a reception IRQ is pending when a mailbox channel is shut down (for example, if the controller uses threaded interrupts), it is possible for mbox_chan_received_data to be called while chan->cl is NULL. This was found while developing a mailbox controller driver for use with SCPI. The SCPI

[PATCH] mailbox: Avoid NULL dereference in mbox_chan_received_data

If a reception IRQ is pending when a mailbox channel is shut down (for example, if the controller uses threaded interrupts), it is possible for mbox_chan_received_data to be called while chan->cl is NULL. This was found while developing a mailbox controller driver for use with SCPI. The SCPI

RE: [PATCH v2 4/4] drivers: firmware: xilinx: Add debugfs interface

Thanks for review Greg, > -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Tuesday, January 23, 2018 12:41 AM > To: Jolly Shah > Cc: ard.biesheu...@linaro.org; mi...@kernel.org; m...@codeblueprint.co.uk; > sudeep.ho...@arm.com;

RE: [PATCH v2 4/4] drivers: firmware: xilinx: Add debugfs interface

Thanks for review Greg, > -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Tuesday, January 23, 2018 12:41 AM > To: Jolly Shah > Cc: ard.biesheu...@linaro.org; mi...@kernel.org; m...@codeblueprint.co.uk; > sudeep.ho...@arm.com; hkallwe...@gmail.com;

RE: [PATCH v2 3/4] drivers: firmware: xilinx: Add sysfs interface

Thanks for review Greg, > -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Tuesday, January 23, 2018 12:38 AM > To: Jolly Shah > Cc: ard.biesheu...@linaro.org; mi...@kernel.org; m...@codeblueprint.co.uk; > sudeep.ho...@arm.com;

RE: [PATCH v2 3/4] drivers: firmware: xilinx: Add sysfs interface

Thanks for review Greg, > -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Tuesday, January 23, 2018 12:38 AM > To: Jolly Shah > Cc: ard.biesheu...@linaro.org; mi...@kernel.org; m...@codeblueprint.co.uk; > sudeep.ho...@arm.com; hkallwe...@gmail.com;

RE: [PATCH v2 2/4] drivers: firmware: xilinx: Add ZynqMP firmware driver

Thanks for review Greg, > -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Tuesday, January 23, 2018 12:38 AM > To: Jolly Shah > Cc: ard.biesheu...@linaro.org; mi...@kernel.org; m...@codeblueprint.co.uk; > sudeep.ho...@arm.com;

RE: [PATCH v2 2/4] drivers: firmware: xilinx: Add ZynqMP firmware driver

Thanks for review Greg, > -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Tuesday, January 23, 2018 12:38 AM > To: Jolly Shah > Cc: ard.biesheu...@linaro.org; mi...@kernel.org; m...@codeblueprint.co.uk; > sudeep.ho...@arm.com; hkallwe...@gmail.com;

[GIT] Sparc

Please pull to get this sparc Makefile typo fix. Thank you. The following changes since commit 0d665e7b109d512b7cae3ccef6e8654714887844: mm, page_vma_mapped: Drop faulty pointer arithmetics in check_pte() (2018-01-21 17:44:47 -0800) are available in the Git repository at:

[GIT] Sparc

Please pull to get this sparc Makefile typo fix. Thank you. The following changes since commit 0d665e7b109d512b7cae3ccef6e8654714887844: mm, page_vma_mapped: Drop faulty pointer arithmetics in check_pte() (2018-01-21 17:44:47 -0800) are available in the Git repository at:

[GIT] Networking

1) Avoid negative netdev refcount in error flow of xfrm state add, from Aviad Yehezkel. 2) Fix tcpdump decoding of IPSEC decap'd frames by filling in the ethernet header protocol field in xfrm{4,6}_mode_tunnel_input(). From Yossi Kuperman. 3) Fix a syzbot triggered skb_under_panic in

[GIT] Networking

1) Avoid negative netdev refcount in error flow of xfrm state add, from Aviad Yehezkel. 2) Fix tcpdump decoding of IPSEC decap'd frames by filling in the ethernet header protocol field in xfrm{4,6}_mode_tunnel_input(). From Yossi Kuperman. 3) Fix a syzbot triggered skb_under_panic in

[PATCH v3 3/4] drivers: firmware: xilinx: Add sysfs interface

Add Firmware-ggs sysfs interface which provides read/write interface to global storage registers. Signed-off-by: Jolly Shah Signed-off-by: Rajan Vaja --- .../ABI/stable/sysfs-driver-zynqmp-firmware| 50 drivers/firmware/xilinx/zynqmp/Makefile

[PATCH v3 3/4] drivers: firmware: xilinx: Add sysfs interface

Add Firmware-ggs sysfs interface which provides read/write interface to global storage registers. Signed-off-by: Jolly Shah Signed-off-by: Rajan Vaja --- .../ABI/stable/sysfs-driver-zynqmp-firmware| 50 drivers/firmware/xilinx/zynqmp/Makefile| 2 +-

[PATCH v3 1/4] dt-bindings: firmware: Add bindings for ZynqMP firmware

Add documentation to describe Xilinx ZynqMP firmware driver bindings. Firmware driver provides an interface to firmware APIs. Interface APIs can be used by any driver to communicate to PMUFW (Platform Management Unit). Signed-off-by: Jolly Shah Signed-off-by: Rajan Vaja

[PATCH v3 1/4] dt-bindings: firmware: Add bindings for ZynqMP firmware

Add documentation to describe Xilinx ZynqMP firmware driver bindings. Firmware driver provides an interface to firmware APIs. Interface APIs can be used by any driver to communicate to PMUFW (Platform Management Unit). Signed-off-by: Jolly Shah Signed-off-by: Rajan Vaja ---

[PATCH v3 2/4] drivers: firmware: xilinx: Add ZynqMP firmware driver

This patch is adding communication layer with firmware. Firmware driver provides an interface to firmware APIs. Interface APIs can be used by any driver to communicate to PMUFW(Platform Management Unit). All requests go through ATF. Signed-off-by: Jolly Shah Signed-off-by:

[PATCH v3 2/4] drivers: firmware: xilinx: Add ZynqMP firmware driver

This patch is adding communication layer with firmware. Firmware driver provides an interface to firmware APIs. Interface APIs can be used by any driver to communicate to PMUFW(Platform Management Unit). All requests go through ATF. Signed-off-by: Jolly Shah Signed-off-by: Rajan Vaja ---

[PATCH v3 4/4] drivers: firmware: xilinx: Add debugfs interface

Firmware-debug provides debugfs interface to all APIs. Signed-off-by: Jolly Shah Signed-off-by: Rajan Vaja --- drivers/firmware/xilinx/zynqmp/Kconfig | 7 + drivers/firmware/xilinx/zynqmp/Makefile| 1 +

[PATCH v3 4/4] drivers: firmware: xilinx: Add debugfs interface

Firmware-debug provides debugfs interface to all APIs. Signed-off-by: Jolly Shah Signed-off-by: Rajan Vaja --- drivers/firmware/xilinx/zynqmp/Kconfig | 7 + drivers/firmware/xilinx/zynqmp/Makefile| 1 + drivers/firmware/xilinx/zynqmp/firmware-debug.c| 511

[PATCH v3 0/4] drivers: firmware: xilinx: Add firmware driver support

Introduce firmware driver for ZynqMP core. This patchset is adding communication layer with firmware. Firmware driver provides an interface to firmware APIs. Interface APIs can be used by any driver to communicate to PMUFW(Platform Management Unit). All requests go through ATF. v3: - added some

[PATCH v3 0/4] drivers: firmware: xilinx: Add firmware driver support

Introduce firmware driver for ZynqMP core. This patchset is adding communication layer with firmware. Firmware driver provides an interface to firmware APIs. Interface APIs can be used by any driver to communicate to PMUFW(Platform Management Unit). All requests go through ATF. v3: - added some

你好！你好吗？

你好！你好吗？

Re: [PATCH v2 2/2] net/ibm/emac: wrong bit is used for STA control register write

From: Ivan Mikhaylov Date: Wed, 24 Jan 2018 15:53:25 +0300 > STA control register has areas of mode and opcodes for opeations. 18 bit is > using for mode selection, where 0 is old MIO/MDIO access method and 1 is > indirect access mode. 19-20 bits are using for setting up

Re: [PATCH v2 1/2] net/ibm/emac: add 8192 rx/tx fifo size

From: Ivan Mikhaylov Date: Wed, 24 Jan 2018 15:53:24 +0300 > emac4syn chips has availability to use 8192 rx/tx fifo buffer sizes, > in current state if we set it up in dts 8192 as example, we will get > only 2048 which may impact on network speed. > > Signed-off-by: Ivan

Re: [PATCH v2 2/2] net/ibm/emac: wrong bit is used for STA control register write

From: Ivan Mikhaylov Date: Wed, 24 Jan 2018 15:53:25 +0300 > STA control register has areas of mode and opcodes for opeations. 18 bit is > using for mode selection, where 0 is old MIO/MDIO access method and 1 is > indirect access mode. 19-20 bits are using for setting up read/write >

Re: [PATCH v2 1/2] net/ibm/emac: add 8192 rx/tx fifo size

From: Ivan Mikhaylov Date: Wed, 24 Jan 2018 15:53:24 +0300 > emac4syn chips has availability to use 8192 rx/tx fifo buffer sizes, > in current state if we set it up in dts 8192 as example, we will get > only 2048 which may impact on network speed. > > Signed-off-by: Ivan Mikhaylov Applied.

Re: [RESEND PATCH 3/6] ARM: dts: imx7s: add CAAM device node

On 24/01/18 22:48, Bryan O'Donoghue wrote: The clock configuration has changed to just one CAAM-specific clock in addition to the ahb clock. This also means that additional modifications to the CAAM driver are necessary or it will complain that it doesn't find all clocks. Sure - but, those

Re: [RESEND PATCH 3/6] ARM: dts: imx7s: add CAAM device node

On 24/01/18 22:48, Bryan O'Donoghue wrote: The clock configuration has changed to just one CAAM-specific clock in addition to the ahb clock. This also means that additional modifications to the CAAM driver are necessary or it will complain that it doesn't find all clocks. Sure - but, those

Re: [PATCH] phy: qcom-ufs: add MODULE_LICENSE tag

On Wed 10 Jan 08:35 PST 2018, Arnd Bergmann wrote: > While the specific UFS PHY drivers (14nm and 20nm) have a module > license, the common base module does not, leading to a Kbuild > failure: > > WARNING: modpost: missing MODULE_LICENSE() in > drivers/phy/qualcomm/phy-qcom-ufs.o > FATAL:

Re: [PATCH] phy: qcom-ufs: add MODULE_LICENSE tag

On Wed 10 Jan 08:35 PST 2018, Arnd Bergmann wrote: > While the specific UFS PHY drivers (14nm and 20nm) have a module > license, the common base module does not, leading to a Kbuild > failure: > > WARNING: modpost: missing MODULE_LICENSE() in > drivers/phy/qualcomm/phy-qcom-ufs.o > FATAL:

Re: [PATCH v3 3/6] x86/cpufeatures: Add AMD feature bits for Speculation Control

On 1/24/2018 11:57 AM, David Woodhouse wrote: > On Wed, 2018-01-24 at 18:20 +0100, Greg KH wrote: >> On Wed, Jan 24, 2018 at 04:57:02PM +, David Woodhouse wrote: >>> >>> AMD exposes the PRED_CMD/SPEC_CTRL MSRs slightly differently to Intel. >>> See

Re: [PATCH v3 3/6] x86/cpufeatures: Add AMD feature bits for Speculation Control

On 1/24/2018 11:57 AM, David Woodhouse wrote: > On Wed, 2018-01-24 at 18:20 +0100, Greg KH wrote: >> On Wed, Jan 24, 2018 at 04:57:02PM +, David Woodhouse wrote: >>> >>> AMD exposes the PRED_CMD/SPEC_CTRL MSRs slightly differently to Intel. >>> See

[PATCH 1/1] scsi: storvsc: Increase cmd_per_lun for higher speed devices

Increase cmd_per_lun to allow more I/Os in progress per device, particularly for NVMe's. The Hyper-V host side can handle the higher count with no issues. Signed-off-by: Michael Kelley --- drivers/scsi/storvsc_drv.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH 1/1] scsi: storvsc: Increase cmd_per_lun for higher speed devices

Increase cmd_per_lun to allow more I/Os in progress per device, particularly for NVMe's. The Hyper-V host side can handle the higher count with no issues. Signed-off-by: Michael Kelley --- drivers/scsi/storvsc_drv.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [RESEND PATCH 3/6] ARM: dts: imx7s: add CAAM device node

On 24/01/18 18:12, Auer, Lukas wrote: On Wed, 2018-01-24 at 14:50 +, Bryan O'Donoghue wrote: From: Rui Miguel Silva Add CAAM device node to the i.MX7s device tree. Signed-off-by: Rui Miguel Silva Cc: "Horia Geantă" Cc:

Re: [RESEND PATCH 3/6] ARM: dts: imx7s: add CAAM device node

On 24/01/18 18:12, Auer, Lukas wrote: On Wed, 2018-01-24 at 14:50 +, Bryan O'Donoghue wrote: From: Rui Miguel Silva Add CAAM device node to the i.MX7s device tree. Signed-off-by: Rui Miguel Silva Cc: "Horia Geantă" Cc: Aymen Sghaier Cc: Fabio Estevam Cc: Peng Fan Cc: Herbert Xu Cc:

Re: Report long suspend times of NVMe devices (mostly firmware/device issues)

On Wed, Jan 24, 2018 at 11:29:12PM +0100, Paul Menzel wrote: > Am 22.01.2018 um 22:30 schrieb Keith Busch: > > The nvme spec guides toward longer times than that. I don't see the > > point of warning users about things operating within spec. > > I quickly glanced over NVM Express revision 1.3

Re: Report long suspend times of NVMe devices (mostly firmware/device issues)

On Wed, Jan 24, 2018 at 11:29:12PM +0100, Paul Menzel wrote: > Am 22.01.2018 um 22:30 schrieb Keith Busch: > > The nvme spec guides toward longer times than that. I don't see the > > point of warning users about things operating within spec. > > I quickly glanced over NVM Express revision 1.3

RE: [PATCH 1/1] scsi: storvsc: Spread interrupts when picking a channel for I/O requests

Updated/corrected two email addresses ... > -Original Message- > From: Michael Kelley (EOSG) > Sent: Wednesday, January 24, 2018 2:14 PM > To: KY Srinivasan ; Stephen Hemminger > ; > martin.peter...@oracle.com; lo...@microsoft.com;

RE: [PATCH 1/1] scsi: storvsc: Spread interrupts when picking a channel for I/O requests

Updated/corrected two email addresses ... > -Original Message- > From: Michael Kelley (EOSG) > Sent: Wednesday, January 24, 2018 2:14 PM > To: KY Srinivasan ; Stephen Hemminger > ; > martin.peter...@oracle.com; lo...@microsoft.com; jbottom...@odin.com; > de...@linuxdriverproject.org;

linux-next: Signed-off-by missing for commits in the tip tree

Hi all, Commits a5d8ae1255fb ("perf vendor events intel: Update Broadwell events to V22") theough 553f486f5129 ("perf vendor events intel: Update IvyTown files to V20") are missing a Signed-off-by from their committer. -- Cheers, Stephen Rothwell

linux-next: Signed-off-by missing for commits in the tip tree

Hi all, Commits a5d8ae1255fb ("perf vendor events intel: Update Broadwell events to V22") theough 553f486f5129 ("perf vendor events intel: Update IvyTown files to V20") are missing a Signed-off-by from their committer. -- Cheers, Stephen Rothwell

Re: Report long suspend times of NVMe devices (mostly firmware/device issues)

Dear Keith, Thank you for your reply. Am 22.01.2018 um 22:30 schrieb Keith Busch: On Mon, Jan 22, 2018 at 10:02:12PM +0100, Paul Menzel wrote: Benchmarking the ACPI S3 suspend and resume times with `sleepgraph.py -config config/suspend-callgraph.cfg` [1], shows that the NVMe disk SAMSUNG

Re: Report long suspend times of NVMe devices (mostly firmware/device issues)

Dear Keith, Thank you for your reply. Am 22.01.2018 um 22:30 schrieb Keith Busch: On Mon, Jan 22, 2018 at 10:02:12PM +0100, Paul Menzel wrote: Benchmarking the ACPI S3 suspend and resume times with `sleepgraph.py -config config/suspend-callgraph.cfg` [1], shows that the NVMe disk SAMSUNG

Re: [patch -mm 3/4] mm, memcg: replace memory.oom_group with policy tunable

Hello, Andrew. On Wed, Jan 24, 2018 at 02:08:05PM -0800, Andrew Morton wrote: > Can we please try to narrow the scope of this issue by concentrating on > the userspace interfaces? David believes that the mount option and > memory.oom_group will disappear again in the near future, others >

Re: [patch -mm 3/4] mm, memcg: replace memory.oom_group with policy tunable

Hello, Andrew. On Wed, Jan 24, 2018 at 02:08:05PM -0800, Andrew Morton wrote: > Can we please try to narrow the scope of this issue by concentrating on > the userspace interfaces? David believes that the mount option and > memory.oom_group will disappear again in the near future, others >

[PATCH 1/1] scsi: storvsc: Spread interrupts when picking a channel for I/O requests

Update the algorithm in storvsc_do_io to look for a channel starting with the current CPU + 1 and wrap around (within the current NUMA node). This spreads VMbus interrupts more evenly across CPUs. Previous code always started with first CPU in the current NUMA node, skewing the interrupt load to

[PATCH 1/1] scsi: storvsc: Spread interrupts when picking a channel for I/O requests

Update the algorithm in storvsc_do_io to look for a channel starting with the current CPU + 1 and wrap around (within the current NUMA node). This spreads VMbus interrupts more evenly across CPUs. Previous code always started with first CPU in the current NUMA node, skewing the interrupt load to

Re: [PATCH] ARM: dts: use a correct at24 fallback for at91-nattis-2-natte-2

Hi Bartosz, On 2018-01-24 22:34, Bartosz Golaszewski wrote: > We now require all at24 users to use the "atmel," fallback in > device tree for different manufacturers. I think my patch [3/4] from about a week ago was just a tiny bit better. https://lkml.org/lkml/2018/1/16/609 Can we please pick

Re: [PATCH] ARM: dts: use a correct at24 fallback for at91-nattis-2-natte-2

Hi Bartosz, On 2018-01-24 22:34, Bartosz Golaszewski wrote: > We now require all at24 users to use the "atmel," fallback in > device tree for different manufacturers. I think my patch [3/4] from about a week ago was just a tiny bit better. https://lkml.org/lkml/2018/1/16/609 Can we please pick

Re: [patch -mm 3/4] mm, memcg: replace memory.oom_group with policy tunable

On Wed, 24 Jan 2018 13:44:02 -0800 (PST) David Rientjes wrote: > On Wed, 24 Jan 2018, Michal Hocko wrote: > > > > The current implementation of memory.oom_group is based on top of a > > > selection implementation that is broken in three ways I have listed for > > >

Re: [patch -mm 3/4] mm, memcg: replace memory.oom_group with policy tunable

On Wed, 24 Jan 2018 13:44:02 -0800 (PST) David Rientjes wrote: > On Wed, 24 Jan 2018, Michal Hocko wrote: > > > > The current implementation of memory.oom_group is based on top of a > > > selection implementation that is broken in three ways I have listed for > > > months: > > > > This

Re: [PATCH v3 1/3] sched/fair: add util_est on top of PELT

On Wed, Jan 24, 2018 at 11:16 AM, Patrick Bellasi wrote: > On 24-Jan 08:40, Joel Fernandes wrote: >> On Tue, Jan 23, 2018 at 10:08 AM, Patrick Bellasi >> wrote: >> > The util_avg signal computed by PELT is too variable for some use-cases. >> >

Re: [PATCH v3 1/3] sched/fair: add util_est on top of PELT

On Wed, Jan 24, 2018 at 11:16 AM, Patrick Bellasi wrote: > On 24-Jan 08:40, Joel Fernandes wrote: >> On Tue, Jan 23, 2018 at 10:08 AM, Patrick Bellasi >> wrote: >> > The util_avg signal computed by PELT is too variable for some use-cases. >> > For example, a big task waking up after a long sleep

Re: [PATCH net 1/2] vhost: use mutex_lock_nested() in vhost_dev_lock_vqs()

From: "Michael S. Tsirkin" Date: Wed, 24 Jan 2018 23:46:19 +0200 > On Wed, Jan 24, 2018 at 04:38:30PM -0500, David Miller wrote: >> From: Jason Wang >> Date: Tue, 23 Jan 2018 17:27:25 +0800 >> >> > We used to call mutex_lock() in vhost_dev_lock_vqs() which

Re: [PATCH net 1/2] vhost: use mutex_lock_nested() in vhost_dev_lock_vqs()

From: "Michael S. Tsirkin" Date: Wed, 24 Jan 2018 23:46:19 +0200 > On Wed, Jan 24, 2018 at 04:38:30PM -0500, David Miller wrote: >> From: Jason Wang >> Date: Tue, 23 Jan 2018 17:27:25 +0800 >> >> > We used to call mutex_lock() in vhost_dev_lock_vqs() which tries to >> > hold mutexes of all

Re: [PATCH] sparc64: fix typo in CONFIG_CRYPTO_DES_SPARC64 => CONFIG_CRYPTO_CAMELLIA_SPARC64

From: Corentin Labbe Date: Tue, 23 Jan 2018 14:33:14 + > This patch fixes the typo CONFIG_CRYPTO_DES_SPARC64 => > CONFIG_CRYPTO_CAMELLIA_SPARC64 > > Fixes: 81658ad0d923 ("sparc64: Add CAMELLIA driver making use of the new > camellia opcodes.") > Signed-off-by:

Re: [PATCH] sparc64: fix typo in CONFIG_CRYPTO_DES_SPARC64 => CONFIG_CRYPTO_CAMELLIA_SPARC64

From: Corentin Labbe Date: Tue, 23 Jan 2018 14:33:14 + > This patch fixes the typo CONFIG_CRYPTO_DES_SPARC64 => > CONFIG_CRYPTO_CAMELLIA_SPARC64 > > Fixes: 81658ad0d923 ("sparc64: Add CAMELLIA driver making use of the new > camellia opcodes.") > Signed-off-by: Corentin Labbe Applied,

Re: [PATCH net 1/2] vhost: use mutex_lock_nested() in vhost_dev_lock_vqs()

On Wed, Jan 24, 2018 at 04:38:30PM -0500, David Miller wrote: > From: Jason Wang > Date: Tue, 23 Jan 2018 17:27:25 +0800 > > > We used to call mutex_lock() in vhost_dev_lock_vqs() which tries to > > hold mutexes of all virtqueues. This may confuse lockdep to report a > >

Re: [PATCH net 1/2] vhost: use mutex_lock_nested() in vhost_dev_lock_vqs()

On Wed, Jan 24, 2018 at 04:38:30PM -0500, David Miller wrote: > From: Jason Wang > Date: Tue, 23 Jan 2018 17:27:25 +0800 > > > We used to call mutex_lock() in vhost_dev_lock_vqs() which tries to > > hold mutexes of all virtqueues. This may confuse lockdep to report a > > possible deadlock

Re: [patch -mm 3/4] mm, memcg: replace memory.oom_group with policy tunable

On Wed, 24 Jan 2018, Michal Hocko wrote: > > The current implementation of memory.oom_group is based on top of a > > selection implementation that is broken in three ways I have listed for > > months: > > This doesn't lead to anywhere. You are not presenting any new arguments > and you are

Re: [patch -mm 3/4] mm, memcg: replace memory.oom_group with policy tunable

On Wed, 24 Jan 2018, Michal Hocko wrote: > > The current implementation of memory.oom_group is based on top of a > > selection implementation that is broken in three ways I have listed for > > months: > > This doesn't lead to anywhere. You are not presenting any new arguments > and you are

[PATCH-next] media: s2255drv: Remove unneeded if else blocks

Given the following definitions from s2255drv.c #define LINE_SZ_4CIFS_NTSC 640 #define LINE_SZ_2CIFS_NTSC 640 #define LINE_SZ_1CIFS_NTSC 320 and #define LINE_SZ_4CIFS_PAL 704 #define LINE_SZ_2CIFS_PAL 704 #define LINE_SZ_1CIFS_PAL 352 f->fmt.pix.width

[PATCH-next] media: s2255drv: Remove unneeded if else blocks

Given the following definitions from s2255drv.c #define LINE_SZ_4CIFS_NTSC 640 #define LINE_SZ_2CIFS_NTSC 640 #define LINE_SZ_1CIFS_NTSC 320 and #define LINE_SZ_4CIFS_PAL 704 #define LINE_SZ_2CIFS_PAL 704 #define LINE_SZ_1CIFS_PAL 352 f->fmt.pix.width

[PATCH] arc: dts: use 'atmel' as manufacturer for at24 in axs10x_mb

Using compatible strings without the part for at24 is now deprecated. Use a correct 'atmel,' value. Signed-off-by: Bartosz Golaszewski --- arch/arc/boot/dts/axs10x_mb.dtsi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/arc/boot/dts/axs10x_mb.dtsi

[PATCH] arc: dts: use 'atmel' as manufacturer for at24 in axs10x_mb

Using compatible strings without the part for at24 is now deprecated. Use a correct 'atmel,' value. Signed-off-by: Bartosz Golaszewski --- arch/arc/boot/dts/axs10x_mb.dtsi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/arc/boot/dts/axs10x_mb.dtsi

[PATCH] powerpc: dts: use 'atmel' as at24 manufacturer for kmcent2

Using compatible strings without the part for at24 is now deprecated. Use a correct 'atmel,' value. Signed-off-by: Bartosz Golaszewski --- arch/powerpc/boot/dts/fsl/kmcent2.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] powerpc: dts: use 'atmel' as at24 manufacturer for kmcent2

Using compatible strings without the part for at24 is now deprecated. Use a correct 'atmel,' value. Signed-off-by: Bartosz Golaszewski --- arch/powerpc/boot/dts/fsl/kmcent2.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/powerpc/boot/dts/fsl/kmcent2.dts

Re: [PATCH net 1/2] vhost: use mutex_lock_nested() in vhost_dev_lock_vqs()

From: Jason Wang Date: Tue, 23 Jan 2018 17:27:25 +0800 > We used to call mutex_lock() in vhost_dev_lock_vqs() which tries to > hold mutexes of all virtqueues. This may confuse lockdep to report a > possible deadlock because of trying to hold locks belong to same > class.

Re: [PATCH net 1/2] vhost: use mutex_lock_nested() in vhost_dev_lock_vqs()

From: Jason Wang Date: Tue, 23 Jan 2018 17:27:25 +0800 > We used to call mutex_lock() in vhost_dev_lock_vqs() which tries to > hold mutexes of all virtqueues. This may confuse lockdep to report a > possible deadlock because of trying to hold locks belong to same > class. Switch to use

[PATCH] powerpc: dts: use a correct at24 compatible fallback in ac14xx

Using 'at24' as fallback is now deprecated - use the full 'atmel,' string. Signed-off-by: Bartosz Golaszewski --- arch/powerpc/boot/dts/ac14xx.dts | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/arch/powerpc/boot/dts/ac14xx.dts

[PATCH] powerpc: dts: use a correct at24 compatible fallback in ac14xx

Using 'at24' as fallback is now deprecated - use the full 'atmel,' string. Signed-off-by: Bartosz Golaszewski --- arch/powerpc/boot/dts/ac14xx.dts | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/arch/powerpc/boot/dts/ac14xx.dts

[PATCH] powerpc: dts: use 'atmel' as at24 anufacturer for pdm360ng

Using 'at' as the part of the compatible string is now deprecated. Use a correct string: 'atmel,'. Signed-off-by: Bartosz Golaszewski --- arch/powerpc/boot/dts/pdm360ng.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/powerpc/boot/dts/pdm360ng.dts

[PATCH] powerpc: dts: use 'atmel' as at24 anufacturer for pdm360ng

Using 'at' as the part of the compatible string is now deprecated. Use a correct string: 'atmel,'. Signed-off-by: Bartosz Golaszewski --- arch/powerpc/boot/dts/pdm360ng.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/powerpc/boot/dts/pdm360ng.dts

[PATCH] ARM: dts: use a correct at24 fallback for at91-nattis-2-natte-2

We now require all at24 users to use the "atmel," fallback in device tree for different manufacturers. Signed-off-by: Bartosz Golaszewski --- arch/arm/boot/dts/at91-nattis-2-natte-2.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] ARM: dts: use a correct at24 fallback for at91-nattis-2-natte-2

We now require all at24 users to use the "atmel," fallback in device tree for different manufacturers. Signed-off-by: Bartosz Golaszewski --- arch/arm/boot/dts/at91-nattis-2-natte-2.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] ARM: dts: consistently use 'atmel' as at24 manufacturer in cyclone5

Using 'at' or 'at24' as the part of the compatible string is now deprecated. Use a correct value: 'atmel,'. Signed-off-by: Bartosz Golaszewski --- arch/arm/boot/dts/socfpga_cyclone5_vining_fpga.dts | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

[PATCH] ARM: dts: consistently use 'atmel' as at24 manufacturer in cyclone5

Using 'at' or 'at24' as the part of the compatible string is now deprecated. Use a correct value: 'atmel,'. Signed-off-by: Bartosz Golaszewski --- arch/arm/boot/dts/socfpga_cyclone5_vining_fpga.dts | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

Re: [PATCH v4] net: qcom/emac: extend DMA mask to 46bits

From: Wang Dongsheng Date: Mon, 22 Jan 2018 20:25:06 -0800 > Bit TPD3[31] is used as a timestamp bit if PTP is enabled, but > it's used as an address bit if PTP is disabled. Since PTP isn't > supported by the driver, we can extend the DMA address to 46 bits. >

Re: [PATCH v4] net: qcom/emac: extend DMA mask to 46bits

From: Wang Dongsheng Date: Mon, 22 Jan 2018 20:25:06 -0800 > Bit TPD3[31] is used as a timestamp bit if PTP is enabled, but > it's used as an address bit if PTP is disabled. Since PTP isn't > supported by the driver, we can extend the DMA address to 46 bits. > > Signed-off-by: Wang Dongsheng

[PATCH 4/4 v2] Input: mms114 - add support for mms152

From: Simon Shields MMS152 has no configuration registers, but the packet format used in interrupts is identical to mms114. Signed-off-by: Simon Shields Patchwork-Id: 10125841 Signed-off-by: Dmitry Torokhov --- V2: Fixed

[PATCH 4/4 v2] Input: mms114 - add support for mms152

From: Simon Shields MMS152 has no configuration registers, but the packet format used in interrupts is identical to mms114. Signed-off-by: Simon Shields Patchwork-Id: 10125841 Signed-off-by: Dmitry Torokhov --- V2: Fixed issue pointed by Marcus Folkesson.

[PATCH] ARM: dts: fix the at24 compatible string in imx6q-h100

Using 'at24' as fallback is now deprecated - use the full 'atmel,' string. Signed-off-by: Bartosz Golaszewski --- arch/arm/boot/dts/imx6q-h100.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/imx6q-h100.dts

[PATCH] ARM: dts: fix the at24 compatible string in imx6q-h100

Using 'at24' as fallback is now deprecated - use the full 'atmel,' string. Signed-off-by: Bartosz Golaszewski --- arch/arm/boot/dts/imx6q-h100.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/imx6q-h100.dts b/arch/arm/boot/dts/imx6q-h100.dts index

[PATCH] ARM: dts: use 'atmel' as at24 manufacturer for imx6qdl-rex

Using 'at' as the part of the compatible string is now deprecated. Use a correct string: 'atmel,'. Signed-off-by: Bartosz Golaszewski --- arch/arm/boot/dts/imx6qdl-rex.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/imx6qdl-rex.dtsi

[PATCH] ARM: dts: use 'atmel' as at24 manufacturer for imx6qdl-rex

Using 'at' as the part of the compatible string is now deprecated. Use a correct string: 'atmel,'. Signed-off-by: Bartosz Golaszewski --- arch/arm/boot/dts/imx6qdl-rex.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/imx6qdl-rex.dtsi

[PATCH] ARM: dts: use 'atmel' as at24 manufacturer for qcom-apq8064-cm-qs600

Using compatible strings without the part for at24 is now deprecated. Use a correct 'atmel,' value. Signed-off-by: Bartosz Golaszewski --- arch/arm/boot/dts/qcom-apq8064-cm-qs600.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] ARM: dts: use 'atmel' as at24 manufacturer for qcom-apq8064-cm-qs600

Using compatible strings without the part for at24 is now deprecated. Use a correct 'atmel,' value. Signed-off-by: Bartosz Golaszewski --- arch/arm/boot/dts/qcom-apq8064-cm-qs600.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/qcom-apq8064-cm-qs600.dts

Re: [PATCH 07/11] signal/arm64: Document conflicts with SI_USER and SIGFPE, SIGTRAP, SIGBUS

Russell King - ARM Linux writes: > On Wed, Jan 17, 2018 at 10:45:10AM -0600, Eric W. Biederman wrote: >> Russell King - ARM Linux writes: >> >From your description there still seems to be an association with an >> instruction so I don't know if I

Re: [PATCH 07/11] signal/arm64: Document conflicts with SI_USER and SIGFPE, SIGTRAP, SIGBUS

Russell King - ARM Linux writes: > On Wed, Jan 17, 2018 at 10:45:10AM -0600, Eric W. Biederman wrote: >> Russell King - ARM Linux writes: >> >From your description there still seems to be an association with an >> instruction so I don't know if I would really call the signal >> asynchronous.

Re: [PATCH v3 6/6] x86/cpufeature: Blacklist SPEC_CTRL on early Spectre v2 microcodes

> On Wed, Jan 24, 2018 at 04:57:05PM +, David Woodhouse wrote: > > +static const struct sku_microcode spectre_bad_microcodes[] = { > > + { INTEL_FAM6_KABYLAKE_DESKTOP, 0x0B, 0x80 }, > > + /* Corrected typo in Intel doc */ > > + { INTEL_FAM6_KABYLAKE_DESKTOP, 0x0A, 0x80 }, > > + {

Re: [PATCH v3 6/6] x86/cpufeature: Blacklist SPEC_CTRL on early Spectre v2 microcodes

> On Wed, Jan 24, 2018 at 04:57:05PM +, David Woodhouse wrote: > > +static const struct sku_microcode spectre_bad_microcodes[] = { > > + { INTEL_FAM6_KABYLAKE_DESKTOP, 0x0B, 0x80 }, > > + /* Corrected typo in Intel doc */ > > + { INTEL_FAM6_KABYLAKE_DESKTOP, 0x0A, 0x80 }, > > + {

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