Re: [PATCH] 8250-men-mcb: add support for 16z025 and 16z057

Hi, Thanks for your comments. Let me briefly respond. On Tue, Feb 27, 2018 at 07:57:34PM +0200, Andy Shevchenko wrote: > On Tue, Feb 27, 2018 at 5:31 PM, Michael Moese wrote: > > - else if (strncmp(mdev->bus->name, "F216", 4) == 0) > > + else if

Re: [PATCH] 8250-men-mcb: add support for 16z025 and 16z057

Hi, Thanks for your comments. Let me briefly respond. On Tue, Feb 27, 2018 at 07:57:34PM +0200, Andy Shevchenko wrote: > On Tue, Feb 27, 2018 at 5:31 PM, Michael Moese wrote: > > - else if (strncmp(mdev->bus->name, "F216", 4) == 0) > > + else if (strncmp(mdev->bus->name, "F216", 4)

Re: [PATCH] usb: dwc3: Prevent indefinite sleep in _dwc3_set_mode during suspend/resume

Hi, Roger Quadros writes: > In the following test we get stuck by sleeping forever in _dwc3_set_mode() > after which dual-role switching doesn't work. > > On dra7-evm's dual-role port, > - Load g_zero gadget driver and enumerate to host > - suspend to mem > - disconnect USB cable

Re: [PATCH] usb: dwc3: Prevent indefinite sleep in _dwc3_set_mode during suspend/resume

Hi, Roger Quadros writes: > In the following test we get stuck by sleeping forever in _dwc3_set_mode() > after which dual-role switching doesn't work. > > On dra7-evm's dual-role port, > - Load g_zero gadget driver and enumerate to host > - suspend to mem > - disconnect USB cable to host and

Re: [PATCH 0/3] STM32 Extended TrustZone Protection driver

2018-02-27 20:46 GMT+01:00 Robin Murphy : > On 27/02/18 19:16, Benjamin Gaignard wrote: >> >> 2018-02-27 18:11 GMT+01:00 Mark Rutland : >>> >>> On Tue, Feb 27, 2018 at 03:09:23PM +0100, Benjamin Gaignard wrote: On early boot stages STM32MP1

Re: [PATCH 0/3] STM32 Extended TrustZone Protection driver

2018-02-27 20:46 GMT+01:00 Robin Murphy : > On 27/02/18 19:16, Benjamin Gaignard wrote: >> >> 2018-02-27 18:11 GMT+01:00 Mark Rutland : >>> >>> On Tue, Feb 27, 2018 at 03:09:23PM +0100, Benjamin Gaignard wrote: On early boot stages STM32MP1 platform is able to dedicate some hardware

[RFC 4/4] trace_uprobe: Fix multiple update of same semaphores

For tiny binaries/libraries, different mmap regions points to the same file portion. In such cases, we may increment semaphore multiple times. But while de-registration, semaphore will get decremented only once, leaving semaphore > 0 even if no one is tracing on that marker. Ensure increment and

[RFC 4/4] trace_uprobe: Fix multiple update of same semaphores

For tiny binaries/libraries, different mmap regions points to the same file portion. In such cases, we may increment semaphore multiple times. But while de-registration, semaphore will get decremented only once, leaving semaphore > 0 even if no one is tracing on that marker. Ensure increment and

[RFC 3/4] trace_uprobe: Support SDT markers having semaphore

Userspace Statically Defined Tracepoints[1] are dtrace style markers inside userspace applications. These markers are added by developer at important places in the code. Each marker source expands to a single nop instruction in the compiled code but there may be additional overhead for computing

[RFC 3/4] trace_uprobe: Support SDT markers having semaphore

Userspace Statically Defined Tracepoints[1] are dtrace style markers inside userspace applications. These markers are added by developer at important places in the code. Each marker source expands to a single nop instruction in the compiled code but there may be additional overhead for computing

[RFC 2/4] Uprobe: Export few functions / data structures

These functions and data structures will be used by other files in later patches. Signed-off-by: Ravi Bangoria --- include/linux/uprobes.h | 23 +++ kernel/events/uprobes.c | 20 ++-- 2 files changed, 29 insertions(+), 14

[RFC 2/4] Uprobe: Export few functions / data structures

These functions and data structures will be used by other files in later patches. Signed-off-by: Ravi Bangoria --- include/linux/uprobes.h | 23 +++ kernel/events/uprobes.c | 20 ++-- 2 files changed, 29 insertions(+), 14 deletions(-) diff --git

[RFC 1/4] Uprobe: Rename map_info to uprobe_map_info

map_info is very generic name, rename it to uprobe_map_info. Renaming will help to export this structure outside of the file. Signed-off-by: Ravi Bangoria --- kernel/events/uprobes.c | 32 +--- 1 file changed, 17 insertions(+), 15

[RFC 1/4] Uprobe: Rename map_info to uprobe_map_info

map_info is very generic name, rename it to uprobe_map_info. Renaming will help to export this structure outside of the file. Signed-off-by: Ravi Bangoria --- kernel/events/uprobes.c | 32 +--- 1 file changed, 17 insertions(+), 15 deletions(-) diff --git

[RFC 0/4] trace_uprobe: Support SDT markers having semaphore

Userspace Statically Defined Tracepoints[1] are dtrace style markers inside userspace applications. These markers are added by developer at important places in the code. Each marker source expands to a single nop instruction in the compiled code but there may be additional overhead for computing

[RFC 0/4] trace_uprobe: Support SDT markers having semaphore

Userspace Statically Defined Tracepoints[1] are dtrace style markers inside userspace applications. These markers are added by developer at important places in the code. Each marker source expands to a single nop instruction in the compiled code but there may be additional overhead for computing

Re: [PATCH v2 4/4] pintcrl: support bias-disable of generic and special pins simultaneously

On Wed, 2018-02-28 at 15:33 +0800, Sean Wang wrote: > On Mon, 2018-02-26 at 16:34 +0800, Zhiyong Tao wrote: > > For generic pins, parameter "arg" is 0 or 1. > > For special pins, bias-disable is set by R0R1, > > so we need transmited "00" to set bias-disable > > When we set "bias-disable" as

Re: [PATCH v2 4/4] pintcrl: support bias-disable of generic and special pins simultaneously

On Wed, 2018-02-28 at 15:33 +0800, Sean Wang wrote: > On Mon, 2018-02-26 at 16:34 +0800, Zhiyong Tao wrote: > > For generic pins, parameter "arg" is 0 or 1. > > For special pins, bias-disable is set by R0R1, > > so we need transmited "00" to set bias-disable > > When we set "bias-disable" as

Re: [PATCH v2 1/4] arm64: dts: mt2712: add pintcrl file

On Wed, 2018-02-28 at 14:42 +0800, Sean Wang wrote: > On Mon, 2018-02-26 at 16:33 +0800, Zhiyong Tao wrote: > > This patch adds pinctrl file for mt2712. > > > > Signed-off-by: Zhiyong Tao > > --- > > arch/arm64/boot/dts/mediatek/mt2712-pinfunc.h | 1129 > >

Re: [PATCH v2 1/4] arm64: dts: mt2712: add pintcrl file

On Wed, 2018-02-28 at 14:42 +0800, Sean Wang wrote: > On Mon, 2018-02-26 at 16:33 +0800, Zhiyong Tao wrote: > > This patch adds pinctrl file for mt2712. > > > > Signed-off-by: Zhiyong Tao > > --- > > arch/arm64/boot/dts/mediatek/mt2712-pinfunc.h | 1129 > > + > > 1 file

RE: [PATCH 0/7] sched/fair: Migrate 'misfit' tasks on asymmetric capacity systems

Hi > -Original Message- > From: linux-kernel-ow...@vger.kernel.org > [mailto:linux-kernel-ow...@vger.kernel.org] On Behalf Of Morten Rasmussen > Sent: Friday, February 16, 2018 1:21 AM > To: pet...@infradead.org; mi...@redhat.com > Cc: valentin.schnei...@arm.com;

RE: [PATCH 0/7] sched/fair: Migrate 'misfit' tasks on asymmetric capacity systems

Hi > -Original Message- > From: linux-kernel-ow...@vger.kernel.org > [mailto:linux-kernel-ow...@vger.kernel.org] On Behalf Of Morten Rasmussen > Sent: Friday, February 16, 2018 1:21 AM > To: pet...@infradead.org; mi...@redhat.com > Cc: valentin.schnei...@arm.com;

Re: [PATCH v2 3/4] pinctrl: add mt2712 pinctrl driver

On Wed, 2018-02-28 at 15:14 +0800, Sean Wang wrote: > Hi, Zhiyong > > all seems better than v1, but some nitpicking is addressed as below > > Sean > > On Mon, 2018-02-26 at 16:34 +0800, Zhiyong Tao wrote: > > The commit includes mt2712 pinctrl driver. > > > > Signed-off-by: Zhiyong Tao

Re: [PATCH v2 3/4] pinctrl: add mt2712 pinctrl driver

On Wed, 2018-02-28 at 15:14 +0800, Sean Wang wrote: > Hi, Zhiyong > > all seems better than v1, but some nitpicking is addressed as below > > Sean > > On Mon, 2018-02-26 at 16:34 +0800, Zhiyong Tao wrote: > > The commit includes mt2712 pinctrl driver. > > > > Signed-off-by: Zhiyong Tao

[PATCH] hwmon: g762: handle cleanup with devm_add_action

Simplify code and use devm_add_action() to handle cleanup. Signed-off-by: Peng Hao --- drivers/hwmon/g762.c | 30 ++ 1 file changed, 14 insertions(+), 16 deletions(-) diff --git a/drivers/hwmon/g762.c b/drivers/hwmon/g762.c index

[PATCH] hwmon: g762: handle cleanup with devm_add_action

Simplify code and use devm_add_action() to handle cleanup. Signed-off-by: Peng Hao --- drivers/hwmon/g762.c | 30 ++ 1 file changed, 14 insertions(+), 16 deletions(-) diff --git a/drivers/hwmon/g762.c b/drivers/hwmon/g762.c index 6d1208b..48e60d8 100644 ---

Re: [PATCH v2 06/16] drm/sun4i: Don't process LVDS if TCON doesn't support it

On Tue, Feb 27, 2018 at 11:26:51PM +0100, Jernej Skrabec wrote: > TCON checks for LVDS properties even if it doesn't support it. Add a > check to skip that part of the code if TCON doesn't support channel 0. > > Signed-off-by: Jernej Skrabec I have already sent a

Re: [PATCH v2 06/16] drm/sun4i: Don't process LVDS if TCON doesn't support it

On Tue, Feb 27, 2018 at 11:26:51PM +0100, Jernej Skrabec wrote: > TCON checks for LVDS properties even if it doesn't support it. Add a > check to skip that part of the code if TCON doesn't support channel 0. > > Signed-off-by: Jernej Skrabec I have already sent a similar patch here:

Re: [PATCH v2 01/16] clk: sunxi-ng: Add check for minimal rate to NM PLLs

Hi, On Tue, Feb 27, 2018 at 11:26:46PM +0100, Jernej Skrabec wrote: > Some NM PLLs doesn't work well when their output clock rate is set below > certain rate. > > Add support for that constrain. > > Signed-off-by: Jernej Skrabec > --- > drivers/clk/sunxi-ng/ccu_nm.c |

Re: [PATCH v2 01/16] clk: sunxi-ng: Add check for minimal rate to NM PLLs

Hi, On Tue, Feb 27, 2018 at 11:26:46PM +0100, Jernej Skrabec wrote: > Some NM PLLs doesn't work well when their output clock rate is set below > certain rate. > > Add support for that constrain. > > Signed-off-by: Jernej Skrabec > --- > drivers/clk/sunxi-ng/ccu_nm.c | 11 +++ >

Re: [PATCH v2 4/4] pintcrl: support bias-disable of generic and special pins simultaneously

On Mon, 2018-02-26 at 16:34 +0800, Zhiyong Tao wrote: > For generic pins, parameter "arg" is 0 or 1. > For special pins, bias-disable is set by R0R1, > so we need transmited "00" to set bias-disable > When we set "bias-disable" as high-z property, > the parameter should be "MTK_PUPD_SET_R1R0_00".

Re: [PATCH v2 4/4] pintcrl: support bias-disable of generic and special pins simultaneously

On Mon, 2018-02-26 at 16:34 +0800, Zhiyong Tao wrote: > For generic pins, parameter "arg" is 0 or 1. > For special pins, bias-disable is set by R0R1, > so we need transmited "00" to set bias-disable > When we set "bias-disable" as high-z property, > the parameter should be "MTK_PUPD_SET_R1R0_00".

Re: [PATCH] ALSA: control: Fix a bunch of whitespace errors

On Tue, 27 Feb 2018 18:29:54 +0100, Richard Fitzgerald wrote: > > Remove a bunch of trailing whitespace errors. They are > fairly annoying if you have your editor set to strip trailing > whitespace because you find you've introduced more changes > than you were trying to make. > > Signed-off-by:

Re: [PATCH] ALSA: control: Fix a bunch of whitespace errors

On Tue, 27 Feb 2018 18:29:54 +0100, Richard Fitzgerald wrote: > > Remove a bunch of trailing whitespace errors. They are > fairly annoying if you have your editor set to strip trailing > whitespace because you find you've introduced more changes > than you were trying to make. > > Signed-off-by:

Re: [RFC PATCH] Take mmap_min_addr into account while choosing unmapped address for x86-64.

On Tue 27-02-18 16:27:29, Ilya Smith wrote: > > > > mmap_min_addr handling is a bit mess... As you say, we would return > > EPERM rather than ENOMEM which can be confusing but depleting the > > address space like that is quite unlikely on 64b unless I am missing. > > It is good to be in sync here

Re: [RFC PATCH] Take mmap_min_addr into account while choosing unmapped address for x86-64.

On Tue 27-02-18 16:27:29, Ilya Smith wrote: > > > > mmap_min_addr handling is a bit mess... As you say, we would return > > EPERM rather than ENOMEM which can be confusing but depleting the > > address space like that is quite unlikely on 64b unless I am missing. > > It is good to be in sync here

Re: [PATCH v2 3/4] pinctrl: add mt2712 pinctrl driver

Hi, Zhiyong all seems better than v1, but some nitpicking is addressed as below Sean On Mon, 2018-02-26 at 16:34 +0800, Zhiyong Tao wrote: > The commit includes mt2712 pinctrl driver. > > Signed-off-by: Zhiyong Tao > --- > drivers/pinctrl/mediatek/Kconfig

Re: [PATCH v2 3/4] pinctrl: add mt2712 pinctrl driver

Hi, Zhiyong all seems better than v1, but some nitpicking is addressed as below Sean On Mon, 2018-02-26 at 16:34 +0800, Zhiyong Tao wrote: > The commit includes mt2712 pinctrl driver. > > Signed-off-by: Zhiyong Tao > --- > drivers/pinctrl/mediatek/Kconfig |7 + >

Re: [PATCH 4.14 00/54] 4.14.23-stable review

On Tue, Feb 27, 2018 at 03:12:02PM -0800, Guenter Roeck wrote: > On Tue, Feb 27, 2018 at 07:36:18PM +0100, Greg Kroah-Hartman wrote: > > On Tue, Feb 27, 2018 at 06:38:59AM -0800, Guenter Roeck wrote: > > > On 02/27/2018 05:08 AM, Greg Kroah-Hartman wrote: > > > > On Tue, Feb 27, 2018 at 02:59:39AM

Re: [PATCH v5 0/4] vm: add a syscall to map a process memory into a pipe

On 02/27/2018 05:18 AM, Dmitry V. Levin wrote: > On Mon, Feb 26, 2018 at 12:02:25PM +0300, Pavel Emelyanov wrote: >> On 02/21/2018 03:44 AM, Andrew Morton wrote: >>> On Tue, 9 Jan 2018 08:30:49 +0200 Mike Rapoport >>> wrote: >>> This patches introduces new

Re: [PATCH 4.14 00/54] 4.14.23-stable review

On Tue, Feb 27, 2018 at 03:12:02PM -0800, Guenter Roeck wrote: > On Tue, Feb 27, 2018 at 07:36:18PM +0100, Greg Kroah-Hartman wrote: > > On Tue, Feb 27, 2018 at 06:38:59AM -0800, Guenter Roeck wrote: > > > On 02/27/2018 05:08 AM, Greg Kroah-Hartman wrote: > > > > On Tue, Feb 27, 2018 at 02:59:39AM

Re: [PATCH v5 0/4] vm: add a syscall to map a process memory into a pipe

On 02/27/2018 05:18 AM, Dmitry V. Levin wrote: > On Mon, Feb 26, 2018 at 12:02:25PM +0300, Pavel Emelyanov wrote: >> On 02/21/2018 03:44 AM, Andrew Morton wrote: >>> On Tue, 9 Jan 2018 08:30:49 +0200 Mike Rapoport >>> wrote: >>> This patches introduces new process_vmsplice system call that

Re: [PATCH v2 07/11] firmware: split firmware fallback functionality into its own file

On Tue, Feb 27, 2018 at 09:33:28PM -0800, Kees Cook wrote: > On Tue, Feb 27, 2018 at 5:28 PM, Luis R. Rodriguez wrote: > > On Tue, Feb 27, 2018 at 03:14:53PM -0800, Kees Cook wrote: > >> On Fri, Feb 23, 2018 at 6:46 PM, Luis R. Rodriguez > >> wrote: > >> >

Re: [PATCH v2 07/11] firmware: split firmware fallback functionality into its own file

On Tue, Feb 27, 2018 at 09:33:28PM -0800, Kees Cook wrote: > On Tue, Feb 27, 2018 at 5:28 PM, Luis R. Rodriguez wrote: > > On Tue, Feb 27, 2018 at 03:14:53PM -0800, Kees Cook wrote: > >> On Fri, Feb 23, 2018 at 6:46 PM, Luis R. Rodriguez > >> wrote: > >> > The firmware fallback code is

[PATCH] staging: android: ashmem: Fix possible deadlock in ashmem_ioctl

ashmem_mutex may create a chain of dependencies like: CPU0CPU1 mmap syscall ioctl syscall -> mmap_sem (acquired) -> ashmem_ioctl -> ashmem_mmap-> ashmem_mutex (acquired) ->

[PATCH] staging: android: ashmem: Fix possible deadlock in ashmem_ioctl

ashmem_mutex may create a chain of dependencies like: CPU0CPU1 mmap syscall ioctl syscall -> mmap_sem (acquired) -> ashmem_ioctl -> ashmem_mmap-> ashmem_mutex (acquired) ->

Re: [RFC REBASED 5/5] powerpc/mm/slice: use the dynamic high slice size to limit bitmap operations

I also noticed that the slice mask printing use wrong variables now. I guess this should take care of it diff --git a/arch/powerpc/mm/slice.c b/arch/powerpc/mm/slice.c index fef3f36b0b73..6b3575c39668 100644 --- a/arch/powerpc/mm/slice.c +++ b/arch/powerpc/mm/slice.c @@ -535,8 +535,6 @@ unsigned

Re: [RFC REBASED 5/5] powerpc/mm/slice: use the dynamic high slice size to limit bitmap operations

I also noticed that the slice mask printing use wrong variables now. I guess this should take care of it diff --git a/arch/powerpc/mm/slice.c b/arch/powerpc/mm/slice.c index fef3f36b0b73..6b3575c39668 100644 --- a/arch/powerpc/mm/slice.c +++ b/arch/powerpc/mm/slice.c @@ -535,8 +535,6 @@ unsigned

[PATCH v2] nvme-multipath: fix sysfs dangerously created links

If multipathing is enabled, each NVMe subsystem creates a head namespace (e.g., nvme0n1) and multiple private namespaces (e.g., nvme0c0n1 and nvme0c1n1) in sysfs. When creating links for private namespaces, links of head namespace are used, so the namespace creation order must be followed (e.g.,

[PATCH v2] nvme-multipath: fix sysfs dangerously created links

If multipathing is enabled, each NVMe subsystem creates a head namespace (e.g., nvme0n1) and multiple private namespaces (e.g., nvme0c0n1 and nvme0c1n1) in sysfs. When creating links for private namespaces, links of head namespace are used, so the namespace creation order must be followed (e.g.,

Re: [PATCH 05/10] hwmon: generic-pwm-tachometer: Add generic PWM based tachometer

On 02/28/2018 08:12 AM, Rajkumar Rampelli wrote: On Wednesday 28 February 2018 11:28 AM, Guenter Roeck wrote: On 02/27/2018 09:38 PM, Rajkumar Rampelli wrote: On Wednesday 21 February 2018 08:20 PM, Guenter Roeck wrote: On 02/20/2018 10:58 PM, Rajkumar Rampelli wrote: Add generic PWM based

Re: [PATCH 05/10] hwmon: generic-pwm-tachometer: Add generic PWM based tachometer

On 02/28/2018 08:12 AM, Rajkumar Rampelli wrote: On Wednesday 28 February 2018 11:28 AM, Guenter Roeck wrote: On 02/27/2018 09:38 PM, Rajkumar Rampelli wrote: On Wednesday 21 February 2018 08:20 PM, Guenter Roeck wrote: On 02/20/2018 10:58 PM, Rajkumar Rampelli wrote: Add generic PWM based

[PATCH] Documentation: Update ncurses package names for menuconfig

The package name is ncurses-devel for Redhat based distros and libncurses-devel for Debian based distros. Signed-off-by: Arvind Prasanna --- scripts/kconfig/lxdialog/check-lxdialog.sh | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git

[PATCH] Documentation: Update ncurses package names for menuconfig

The package name is ncurses-devel for Redhat based distros and libncurses-devel for Debian based distros. Signed-off-by: Arvind Prasanna --- scripts/kconfig/lxdialog/check-lxdialog.sh | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git

Re: [RFC REBASED 5/5] powerpc/mm/slice: use the dynamic high slice size to limit bitmap operations

On 02/28/2018 12:23 PM, Nicholas Piggin wrote: On Tue, 27 Feb 2018 18:11:07 +0530 "Aneesh Kumar K.V" wrote: Nicholas Piggin writes: On Tue, 27 Feb 2018 14:31:07 +0530 "Aneesh Kumar K.V" wrote:

Re: [RFC REBASED 5/5] powerpc/mm/slice: use the dynamic high slice size to limit bitmap operations

On 02/28/2018 12:23 PM, Nicholas Piggin wrote: On Tue, 27 Feb 2018 18:11:07 +0530 "Aneesh Kumar K.V" wrote: Nicholas Piggin writes: On Tue, 27 Feb 2018 14:31:07 +0530 "Aneesh Kumar K.V" wrote: Christophe Leroy writes: The number of high slices a process might use now depends

Re: [PATCH RESEND v5 2/2] KVM: X86: Allow userspace to define the microcode version

On 28/02/2018 07:03, Wanpeng Li wrote: > From: Wanpeng Li > > Linux (among the others) has checks to make sure that certain features > aren't enabled on a certain family/model/stepping if the microcode version > isn't greater than or equal to a known good version. > >

Re: [PATCH RESEND v5 2/2] KVM: X86: Allow userspace to define the microcode version

On 28/02/2018 07:03, Wanpeng Li wrote: > From: Wanpeng Li > > Linux (among the others) has checks to make sure that certain features > aren't enabled on a certain family/model/stepping if the microcode version > isn't greater than or equal to a known good version. > > By exposing the real

[PATCH] dma-buf/reservation: shouldn't kfree staged when slot available

under below scenario the obj->fence would refer to a wild pointer: 1,call reservation_object_reserved_shared 2,call reservation_object_add_shared_fence 3,call reservation_object_reserved_shared 4,call reservation_object_add_shared_fence in step 1, staged is allocated, in step 2, code path will

[PATCH] dma-buf/reservation: shouldn't kfree staged when slot available

under below scenario the obj->fence would refer to a wild pointer: 1,call reservation_object_reserved_shared 2,call reservation_object_add_shared_fence 3,call reservation_object_reserved_shared 4,call reservation_object_add_shared_fence in step 1, staged is allocated, in step 2, code path will

Re: [PATCH RESEND v5 1/2] KVM: X86: Introduce kvm_get_msr_feature()

On 28/02/2018 07:03, Wanpeng Li wrote: > From: Wanpeng Li > > Introduce kvm_get_msr_feature() to handle the msrs which are supported > by different vendors and sharing the same emulation logic. > > Cc: Paolo Bonzini > Cc: Radim Krčmář

Re: [PATCH RESEND v5 1/2] KVM: X86: Introduce kvm_get_msr_feature()

On 28/02/2018 07:03, Wanpeng Li wrote: > From: Wanpeng Li > > Introduce kvm_get_msr_feature() to handle the msrs which are supported > by different vendors and sharing the same emulation logic. > > Cc: Paolo Bonzini > Cc: Radim Krčmář > Cc: Liran Alon > Cc: Nadav Amit > Cc: Borislav Petkov

Re: [RFC REBASED 5/5] powerpc/mm/slice: use the dynamic high slice size to limit bitmap operations

On Tue, 27 Feb 2018 18:11:07 +0530 "Aneesh Kumar K.V" wrote: > Nicholas Piggin writes: > > > On Tue, 27 Feb 2018 14:31:07 +0530 > > "Aneesh Kumar K.V" wrote: > > > >> Christophe Leroy

Re: [RFC REBASED 5/5] powerpc/mm/slice: use the dynamic high slice size to limit bitmap operations

On Tue, 27 Feb 2018 18:11:07 +0530 "Aneesh Kumar K.V" wrote: > Nicholas Piggin writes: > > > On Tue, 27 Feb 2018 14:31:07 +0530 > > "Aneesh Kumar K.V" wrote: > > > >> Christophe Leroy writes: > >> > >> > The number of high slices a process might use now depends on its > >> > address

[PATCH][V2] firmware: dmi_scan: add DMI_OEM_STRING support to dmi_matches

OEM strings are defined by each OEM and they contain customized and useful OEM information. Supporting it provides more flexible uses of the dmi_matches function. Signed-off-by: Alex Hung --- drivers/firmware/dmi_scan.c | 11 +--

[PATCH][V2] firmware: dmi_scan: add DMI_OEM_STRING support to dmi_matches

OEM strings are defined by each OEM and they contain customized and useful OEM information. Supporting it provides more flexible uses of the dmi_matches function. Signed-off-by: Alex Hung --- drivers/firmware/dmi_scan.c | 11 +-- include/linux/mod_devicetable.h | 1 + 2 files

maybe a bug in SELinux: security_context_to_sid_core

Hi, Before SELinux is initialized, get scontext by secid by using: security_secctx_to_secid() may return wrong numbe eg: security_secctx_to_secid("devnull", strlen("devnull"), ); sid here will be 1 because: in security_context_to_sid_core: ... if (!ss_initialized) {

maybe a bug in SELinux: security_context_to_sid_core

Hi, Before SELinux is initialized, get scontext by secid by using: security_secctx_to_secid() may return wrong numbe eg: security_secctx_to_secid("devnull", strlen("devnull"), ); sid here will be 1 because: in security_context_to_sid_core: ... if (!ss_initialized) {

Re: [PATCH] staging:r8188eu: use lib80211 CCMP decrypt

Hm... Sorry. I was looking at the wrong code. I was looking at aes_decipher() instead of rtw_aes_decrypt(). The aes_decipher() was acceptable style (although, it's of course good that you deleted it). rtw_aes_decrypt() was always really really awful. That's fine then. Sorry again. regards,

Re: [PATCH] staging:r8188eu: use lib80211 CCMP decrypt

Hm... Sorry. I was looking at the wrong code. I was looking at aes_decipher() instead of rtw_aes_decrypt(). The aes_decipher() was acceptable style (although, it's of course good that you deleted it). rtw_aes_decrypt() was always really really awful. That's fine then. Sorry again. regards,

[PATCH] nios2: Use read_persistent_clock64() instead of read_persistent_clock()

Since struct timespec is not y2038 safe on 32bit machines, this patch converts read_persistent_clock() to read_persistent_clock64() using struct timespec64, as well as converting mktime() to mktime64(). Signed-off-by: Baolin Wang --- arch/nios2/kernel/time.c |4 ++--

[PATCH] nios2: Use read_persistent_clock64() instead of read_persistent_clock()

Since struct timespec is not y2038 safe on 32bit machines, this patch converts read_persistent_clock() to read_persistent_clock64() using struct timespec64, as well as converting mktime() to mktime64(). Signed-off-by: Baolin Wang --- arch/nios2/kernel/time.c |4 ++-- 1 file changed, 2

Re: [PATCH v2 1/4] arm64: dts: mt2712: add pintcrl file

On Mon, 2018-02-26 at 16:33 +0800, Zhiyong Tao wrote: > This patch adds pinctrl file for mt2712. > > Signed-off-by: Zhiyong Tao > --- > arch/arm64/boot/dts/mediatek/mt2712-pinfunc.h | 1129 > + > 1 file changed, 1129 insertions(+) > create

Re: [PATCH v2 1/4] arm64: dts: mt2712: add pintcrl file

On Mon, 2018-02-26 at 16:33 +0800, Zhiyong Tao wrote: > This patch adds pinctrl file for mt2712. > > Signed-off-by: Zhiyong Tao > --- > arch/arm64/boot/dts/mediatek/mt2712-pinfunc.h | 1129 > + > 1 file changed, 1129 insertions(+) > create mode 100644

Re: [PATCH v4 4/6] arm64: dts: exynos: add OF graph between MHL and USB connector

On 27.02.2018 22:24, Rob Herring wrote: > On Wed, Feb 21, 2018 at 2:55 AM, Andrzej Hajda wrote: >> OF graph describes MHL data lanes between MHL and respective USB >> connector. >> >> Signed-off-by: Andrzej Hajda >> --- >> v4: >> - added missing reg

Re: [PATCH v4 4/6] arm64: dts: exynos: add OF graph between MHL and USB connector

On 27.02.2018 22:24, Rob Herring wrote: > On Wed, Feb 21, 2018 at 2:55 AM, Andrzej Hajda wrote: >> OF graph describes MHL data lanes between MHL and respective USB >> connector. >> >> Signed-off-by: Andrzej Hajda >> --- >> v4: >> - added missing reg property in connector's port node (Krzysztof)

Re: [PATCH] ARM: davinci: fix the GPIO lookup for omapl138-hawk

On Tuesday 27 February 2018 05:44 PM, Bartosz Golaszewski wrote: > From: Bartosz Golaszewski > > The GPIO chip is called davinci_gpio.0 in legacy mode. Fix it, so that > mmc can correctly lookup the wp and cp gpios. > > Signed-off-by: Bartosz Golaszewski

Re: [PATCH] ARM: davinci: fix the GPIO lookup for omapl138-hawk

On Tuesday 27 February 2018 05:44 PM, Bartosz Golaszewski wrote: > From: Bartosz Golaszewski > > The GPIO chip is called davinci_gpio.0 in legacy mode. Fix it, so that > mmc can correctly lookup the wp and cp gpios. > > Signed-off-by: Bartosz Golaszewski > --- >

[PATCH v2 6/6] MAINTAINERS: Add entry for Jailhouse

From: Jan Kiszka Signed-off-by: Jan Kiszka --- MAINTAINERS | 7 +++ 1 file changed, 7 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 93a12af4f180..4b889f282c77 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -7521,6 +7521,13 @@ Q:

[PATCH v2 6/6] MAINTAINERS: Add entry for Jailhouse

From: Jan Kiszka Signed-off-by: Jan Kiszka --- MAINTAINERS | 7 +++ 1 file changed, 7 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 93a12af4f180..4b889f282c77 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -7521,6 +7521,13 @@ Q:

[PATCH v2 5/6] x86/jailhouse: Allow to use PCI_MMCONFIG without ACPI

From: Jan Kiszka Jailhouse does not use ACPI, but it does support MMCONFIG. Make sure the latter can be built without having to enable ACPI as well. Primarily, we need to make the AMD mmconf-fam10h_64 depend upon MMCONFIG and ACPI, instead of just the former. Saves some

[PATCH v2 5/6] x86/jailhouse: Allow to use PCI_MMCONFIG without ACPI

From: Jan Kiszka Jailhouse does not use ACPI, but it does support MMCONFIG. Make sure the latter can be built without having to enable ACPI as well. Primarily, we need to make the AMD mmconf-fam10h_64 depend upon MMCONFIG and ACPI, instead of just the former. Saves some bytes in the Jailhouse

[PATCH v2 3/6] x86/jailhouse: Enable PCI mmconfig access in inmates

From: Otavio Pontes Use the PCI mmconfig base address exported by jailhouse in boot parameters in order to access the memory mapped PCI configuration space. Signed-off-by: Otavio Pontes [Jan: rebased, fixed !CONFIG_PCI_MMCONFIG] Signed-off-by:

[PATCH v2 3/6] x86/jailhouse: Enable PCI mmconfig access in inmates

From: Otavio Pontes Use the PCI mmconfig base address exported by jailhouse in boot parameters in order to access the memory mapped PCI configuration space. Signed-off-by: Otavio Pontes [Jan: rebased, fixed !CONFIG_PCI_MMCONFIG] Signed-off-by: Jan Kiszka --- arch/x86/include/asm/pci_x86.h |

[PATCH v2 1/6] jailhouse: Provide detection for non-x86 systems

From: Jan Kiszka Implement jailhouse_paravirt() via device tree probing on architectures != x86. Will be used by the PCI core. CC: Rob Herring CC: Mark Rutland Signed-off-by: Jan Kiszka ---

[PATCH v2 1/6] jailhouse: Provide detection for non-x86 systems

From: Jan Kiszka Implement jailhouse_paravirt() via device tree probing on architectures != x86. Will be used by the PCI core. CC: Rob Herring CC: Mark Rutland Signed-off-by: Jan Kiszka --- Documentation/devicetree/bindings/jailhouse.txt | 8 arch/x86/include/asm/jailhouse_para.h

[PATCH v2 0/6] jailhouse: Enhance secondary Jailhouse guest support /wrt PCI

Basic x86 support [1] for running Linux as secondary Jailhouse [2] guest is currently pending in the tip tree. This builds on top and enhances the PCI support for x86 and also ARM guests (ARM[64] does not require platform patches and works already). Key elements of this series are: - detection

[PATCH v2 4/6] x86: Consolidate PCI_MMCONFIG configs

From: Jan Kiszka Not sure if those two worked by design or just by chance so far. In any case, it's at least cleaner and clearer to express this in a single config statement. Signed-off-by: Jan Kiszka --- arch/x86/Kconfig | 9 +++-- 1 file

[PATCH v2 0/6] jailhouse: Enhance secondary Jailhouse guest support /wrt PCI

Basic x86 support [1] for running Linux as secondary Jailhouse [2] guest is currently pending in the tip tree. This builds on top and enhances the PCI support for x86 and also ARM guests (ARM[64] does not require platform patches and works already). Key elements of this series are: - detection

[PATCH v2 4/6] x86: Consolidate PCI_MMCONFIG configs

From: Jan Kiszka Not sure if those two worked by design or just by chance so far. In any case, it's at least cleaner and clearer to express this in a single config statement. Signed-off-by: Jan Kiszka --- arch/x86/Kconfig | 9 +++-- 1 file changed, 3 insertions(+), 6 deletions(-) diff

[PATCH v2 2/6] PCI: Scan all functions when running over Jailhouse

From: Jan Kiszka Per PCIe r4.0, sec 7.5.1.1.9, multi-function devices are required to have a function 0. Therefore, Linux scans for devices at function 0 (devfn 0/8/16/...) and only scans for other functions if function 0 has its Multi-Function Device bit set or ARI or

[PATCH v2 2/6] PCI: Scan all functions when running over Jailhouse

From: Jan Kiszka Per PCIe r4.0, sec 7.5.1.1.9, multi-function devices are required to have a function 0. Therefore, Linux scans for devices at function 0 (devfn 0/8/16/...) and only scans for other functions if function 0 has its Multi-Function Device bit set or ARI or SR-IOV indicate there are

Re: [alsa-devel] [PATCH 0/1] Re: Applied "ASoC: topology: Fix logical inversion in set_link_hw_format()" to the asoc tree

On 2/27/18 12:33 PM, Kirill Marinushkin wrote: Hello Mark, Pierre-Louis, Pan, Liam, As there are too much open questions regarding the bclk and fsync inversion in set_link_hw_format(), I would like to suggest the alternative solution. This solution will fit both use-cases: * existing

Re: [PATCH 1/2] ARM: dts: imx6: RDU2: Add RAVE SP device

On Mon, Feb 26, 2018 at 06:49:41AM -0800, Andrey Smirnov wrote: > With MFD and watchdog drivers for RAVE SP device support added by > 538ee27290fa ("mfd: Add driver for RAVE Supervisory Processor") and > c3bb33345721 ("watchdog: Add RAVE SP watchdog driver") add > corresponding DT node for RDU2. >

Re: [alsa-devel] [PATCH 0/1] Re: Applied "ASoC: topology: Fix logical inversion in set_link_hw_format()" to the asoc tree

On 2/27/18 12:33 PM, Kirill Marinushkin wrote: Hello Mark, Pierre-Louis, Pan, Liam, As there are too much open questions regarding the bclk and fsync inversion in set_link_hw_format(), I would like to suggest the alternative solution. This solution will fit both use-cases: * existing

Re: [PATCH 1/2] ARM: dts: imx6: RDU2: Add RAVE SP device

On Mon, Feb 26, 2018 at 06:49:41AM -0800, Andrey Smirnov wrote: > With MFD and watchdog drivers for RAVE SP device support added by > 538ee27290fa ("mfd: Add driver for RAVE Supervisory Processor") and > c3bb33345721 ("watchdog: Add RAVE SP watchdog driver") add > corresponding DT node for RDU2. >

Re: [PATCH] init/Kconfig: make CHECKPOINT_RESTORE select PROC_PAGE_MONITOR

Hi Mike, I love your patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.16-rc3 next-20180227] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits

Re: [PATCH] init/Kconfig: make CHECKPOINT_RESTORE select PROC_PAGE_MONITOR

Hi Mike, I love your patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.16-rc3 next-20180227] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits

[PATCH] m68k: Use read_persistent_clock64() instead of read_persistent_clock()

Since struct timespec is not y2038 safe on 32bit machines, this patch converts read_persistent_clock() to read_persistent_clock64() using struct timespec64, as well as converting mktime() to mktime64(). Signed-off-by: Baolin Wang --- arch/m68k/kernel/time.c |4 ++--

[PATCH] m68k: Use read_persistent_clock64() instead of read_persistent_clock()

Since struct timespec is not y2038 safe on 32bit machines, this patch converts read_persistent_clock() to read_persistent_clock64() using struct timespec64, as well as converting mktime() to mktime64(). Signed-off-by: Baolin Wang --- arch/m68k/kernel/time.c |4 ++-- 1 file changed, 2

  1   2   3   4   5   6   7   8   9   10   >