Re: [PATCH] ideapad-laptop: add a new WMI string for ESC key

On Mon, May 09, 2016 at 11:49:21PM +0200, Arnd Bergmann wrote: > My patch to the ideapad-laptop driver to get the ESC key working on the > Yoga 1170 (Yoga 3) failed to do the same for the following model, the > Lenovo Yoga 700. > > Denis Gordienko managed to get it working by adding another GUID

Re: [PATCH] ideapad-laptop: add a new WMI string for ESC key

On Mon, May 09, 2016 at 11:49:21PM +0200, Arnd Bergmann wrote: > My patch to the ideapad-laptop driver to get the ESC key working on the > Yoga 1170 (Yoga 3) failed to do the same for the following model, the > Lenovo Yoga 700. > > Denis Gordienko managed to get it working by adding another GUID

Re: [PATCH v6 00/13] x86/xsaves: Fix XSAVES issues

On Wed, May 11, 2016 at 06:17:41AM +0200, Borislav Petkov wrote: > Please, for the future, do send your patchset roughly only once a week - > you just sent v5 a day or two ago without giving proper time to people > (me?) to review them all. Consult Documentation/SubmittingPatches if > there are

Re: [PATCH v6 00/13] x86/xsaves: Fix XSAVES issues

On Wed, May 11, 2016 at 06:17:41AM +0200, Borislav Petkov wrote: > Please, for the future, do send your patchset roughly only once a week - > you just sent v5 a day or two ago without giving proper time to people > (me?) to review them all. Consult Documentation/SubmittingPatches if > there are

Re: [PATCH] cocci: Provide script to find i2c_tables missing exports

Hello Kieran, Thanks for the patch, it would be great to automate this to avoid new drivers to introduce new issues! On 05/10/2016 11:07 AM, Kieran Bingham wrote: > Adds MODULE_DEVICE_TABLE(i2c, ...) to correctly export tables in i2c drivers > --- > Ahem, My appologies, I wrongly sent the patch

Re: [PATCH] cocci: Provide script to find i2c_tables missing exports

Hello Kieran, Thanks for the patch, it would be great to automate this to avoid new drivers to introduce new issues! On 05/10/2016 11:07 AM, Kieran Bingham wrote: > Adds MODULE_DEVICE_TABLE(i2c, ...) to correctly export tables in i2c drivers > --- > Ahem, My appologies, I wrongly sent the patch

Re: [PATCH V4 3/3] soc/tegra: pmc: Add support for IO pads power state and voltage

On 11/05/16 18:22, Laxman Dewangan wrote: > > On Wednesday 11 May 2016 09:05 PM, Jon Hunter wrote: >> On 11/05/16 14:28, Laxman Dewangan wrote: >>> On Sunday 08 May 2016 05:43 PM, Jon Hunter wrote: On 06/05/16 16:32, Laxman Dewangan wrote: > On Friday 06 May 2016 08:07 PM, Jon Hunter

[PATCH v7 08/13] x86/xsaves: Fix XSTATE component offset print out

Component offset print out was incorrect for XSAVES. Correct it and move to a separate function. Signed-off-by: Yu-cheng Yu Reviewed-by: Dave Hansen --- arch/x86/kernel/fpu/xstate.c | 18 -- 1 file changed, 16 insertions(+), 2

Re: [PATCH V4 3/3] soc/tegra: pmc: Add support for IO pads power state and voltage

On 11/05/16 18:22, Laxman Dewangan wrote: > > On Wednesday 11 May 2016 09:05 PM, Jon Hunter wrote: >> On 11/05/16 14:28, Laxman Dewangan wrote: >>> On Sunday 08 May 2016 05:43 PM, Jon Hunter wrote: On 06/05/16 16:32, Laxman Dewangan wrote: > On Friday 06 May 2016 08:07 PM, Jon Hunter

[PATCH v7 08/13] x86/xsaves: Fix XSTATE component offset print out

Component offset print out was incorrect for XSAVES. Correct it and move to a separate function. Signed-off-by: Yu-cheng Yu Reviewed-by: Dave Hansen --- arch/x86/kernel/fpu/xstate.c | 18 -- 1 file changed, 16 insertions(+), 2 deletions(-) diff --git

[PATCH v7 09/13] x86/xsaves: Fix xstate_offsets, xstate_sizes for non-extended states

The arrays xstate_offsets[] and xstate_sizes[] record XSAVE standard- format offsets and sizes. Values for non-extended state components fpu and xmm's were not initialized or used. Ptrace format conversion needs them. Fix it. Signed-off-by: Yu-cheng Yu Reviewed-by: Dave

[PATCH v7 06/13] x86/xsaves: Supervisor state component offset

CPUID function 0x0d, sub function (i, i > 1) returns in ebx the offset of xstate component i. Zero is returned for a supervisor state. A supervisor state can only be saved by XSAVES and XSAVES uses a compacted format. There is no fixed offset for a supervisor state. This patch checks and makes

[PATCH v7 00/13] x86/xsaves: Fix XSAVES issues

XSAVES is a kernel-mode instruction. It offers a compacted format and memory-write optimization. These patches fix issues in the first implementation. Changes since Version 6: There are no functional or code changes, only some cleanup work: Patch 1 ~ 4: Fix Signed-off-by chain. Patch 11,

[PATCH v7 00/13] x86/xsaves: Fix XSAVES issues

XSAVES is a kernel-mode instruction. It offers a compacted format and memory-write optimization. These patches fix issues in the first implementation. Changes since Version 6: There are no functional or code changes, only some cleanup work: Patch 1 ~ 4: Fix Signed-off-by chain. Patch 11,

[PATCH v7 09/13] x86/xsaves: Fix xstate_offsets, xstate_sizes for non-extended states

The arrays xstate_offsets[] and xstate_sizes[] record XSAVE standard- format offsets and sizes. Values for non-extended state components fpu and xmm's were not initialized or used. Ptrace format conversion needs them. Fix it. Signed-off-by: Yu-cheng Yu Reviewed-by: Dave Hansen ---

[PATCH v7 06/13] x86/xsaves: Supervisor state component offset

CPUID function 0x0d, sub function (i, i > 1) returns in ebx the offset of xstate component i. Zero is returned for a supervisor state. A supervisor state can only be saved by XSAVES and XSAVES uses a compacted format. There is no fixed offset for a supervisor state. This patch checks and makes

[PATCH v7 10/13] x86/xsaves: Fix __fpu_restore_sig() for XSAVES

When the kernel is using XSAVES compacted format, we cannot do __copy_from_user() from a signal frame, which has standard-format data. Fix it by using copyin_to_xsaves(), which converts between formats and filters out all supervisor states that we do not allow userspace to write. Signed-off-by:

[PATCH v7 12/13] x86/xsaves: Fix fpstate_init() for XRSTORS

In XSAVES mode if fpstate_init() is used to initialize a task's extended state area, xsave.header.xcomp_bv[63] must be set. Otherwise, when the task is scheduled, a warning is triggered from copy_kernel_to_xregs(). One such test case is: setting an invalid extended state through PTRACE. When

[PATCH v7 10/13] x86/xsaves: Fix __fpu_restore_sig() for XSAVES

When the kernel is using XSAVES compacted format, we cannot do __copy_from_user() from a signal frame, which has standard-format data. Fix it by using copyin_to_xsaves(), which converts between formats and filters out all supervisor states that we do not allow userspace to write. Signed-off-by:

[PATCH v7 12/13] x86/xsaves: Fix fpstate_init() for XRSTORS

In XSAVES mode if fpstate_init() is used to initialize a task's extended state area, xsave.header.xcomp_bv[63] must be set. Otherwise, when the task is scheduled, a warning is triggered from copy_kernel_to_xregs(). One such test case is: setting an invalid extended state through PTRACE. When

Re: [PATCH v7 00/13] x86/xsaves: Fix XSAVES issues

On Wed, May 11, 2016 at 12:51:03PM -0700, Yu-cheng Yu wrote: > XSAVES is a kernel-mode instruction. It offers a compacted format and > memory-write optimization. These patches fix issues in the first > implementation. Dude, do you even read my emails?!

Re: [PATCH v7 00/13] x86/xsaves: Fix XSAVES issues

On Wed, May 11, 2016 at 12:51:03PM -0700, Yu-cheng Yu wrote: > XSAVES is a kernel-mode instruction. It offers a compacted format and > memory-write optimization. These patches fix issues in the first > implementation. Dude, do you even read my emails?!

[PATCH v7 11/13] x86/xsaves: When a disabled xstate component address is requested, return NULL

It is an error to request a disabled XSAVE/XSAVES component address. For that case, make __raw_xsave_addr() return a NULL and issue a warning. Signed-off-by: Yu-cheng Yu Reviewed-by: Dave Hansen --- arch/x86/kernel/fpu/xstate.c | 5 + 1 file

[PATCH v7 11/13] x86/xsaves: When a disabled xstate component address is requested, return NULL

It is an error to request a disabled XSAVE/XSAVES component address. For that case, make __raw_xsave_addr() return a NULL and issue a warning. Signed-off-by: Yu-cheng Yu Reviewed-by: Dave Hansen --- arch/x86/kernel/fpu/xstate.c | 5 + 1 file changed, 5 insertions(+) diff --git

[PATCH v7 07/13] x86/xsaves: Fix PTRACE frames for XSAVES

XSAVES uses compacted format and is a kernel instruction. The kernel should use standard-format, non-supervisor state data for PTRACE. Signed-off-by: Yu-cheng Yu Reviewed-by: Dave Hansen --- arch/x86/include/asm/fpu/xstate.h | 5 +-

Re: [Patch v4 3/8] firmware: qcom: scm: Use atomic SCM for cold boot

On Wed 11 May 07:15 PDT 2016, Andy Gross wrote: > This patch changes the cold_set_boot_addr function to use atomic SCM > calls. cold_set_boot_addr required adding qcom_scm_call_atomic2 to > support the two arguments going to the smc call. Using atomic removes > the need for memory allocation

[PATCH v7 07/13] x86/xsaves: Fix PTRACE frames for XSAVES

XSAVES uses compacted format and is a kernel instruction. The kernel should use standard-format, non-supervisor state data for PTRACE. Signed-off-by: Yu-cheng Yu Reviewed-by: Dave Hansen --- arch/x86/include/asm/fpu/xstate.h | 5 +- arch/x86/kernel/fpu/regset.c | 56 +

Re: [Patch v4 3/8] firmware: qcom: scm: Use atomic SCM for cold boot

On Wed 11 May 07:15 PDT 2016, Andy Gross wrote: > This patch changes the cold_set_boot_addr function to use atomic SCM > calls. cold_set_boot_addr required adding qcom_scm_call_atomic2 to > support the two arguments going to the smc call. Using atomic removes > the need for memory allocation

[PATCH v7 13/13] x86/xsaves: Re-enable XSAVES

We did not handle XSAVES instructions correctly. There were issues in converting between standard and compacted format when interfacing with user-space. These issues have been corrected. Add a WARN_ONCE() to make it clear that XSAVES supervisor states are not yet implemented. Signed-off-by:

[PATCH v7 13/13] x86/xsaves: Re-enable XSAVES

We did not handle XSAVES instructions correctly. There were issues in converting between standard and compacted format when interfacing with user-space. These issues have been corrected. Add a WARN_ONCE() to make it clear that XSAVES supervisor states are not yet implemented. Signed-off-by:

[GIT PULL] SCSI fixes for 4.6-rc2

This is a couple of small fixes: one is a potential uninitialised error variable in the alua code, potentially causing spurious failures and the other is a problem caused by the conversion of SCSI to hostwide tags which resulted in the qla1280 driver always failing in host initialisation. The

[GIT PULL] SCSI fixes for 4.6-rc2

This is a couple of small fixes: one is a potential uninitialised error variable in the alua code, potentially causing spurious failures and the other is a problem caused by the conversion of SCSI to hostwide tags which resulted in the qla1280 driver always failing in host initialisation. The

[PATCH v7 05/13] x86/xsaves: Align xstate components according to CPUID

CPUID function 0x0d, sub function (i, i > 1) returns in ecx[1] the alignment requirement of component i when the compacted format is used. If ecx[1] is 0, component i is located immediately following the preceding component. If ecx[1] is 1, component i is located on the next 64-byte boundary

[PATCH v7 05/13] x86/xsaves: Align xstate components according to CPUID

CPUID function 0x0d, sub function (i, i > 1) returns in ecx[1] the alignment requirement of component i when the compacted format is used. If ecx[1] is 0, component i is located immediately following the preceding component. If ecx[1] is 1, component i is located on the next 64-byte boundary

[PATCH v7 02/13] x86/xsaves: Rename xstate_size to fpu_kernel_xstate_size to distinguish from fpu_user_xstate_size

From: Fenghua Yu User space uses standard format xsave area. fpstate in signal frame should have standard format size. To explicitly distinguish between xstate size in kernel space and the one in user space, we rename xstate_size to fpu_kernel_xstate_size. This patch is

[PATCH v7 04/13] x86/xsaves: Introduce a new check that allows correct xstates copy from kernel to user directly

XSAVES is a kernel instruction and uses a compacted format. When working with user space, the kernel should provide standard-format, non-supervisor state data. We cannot do __copy_to_user() from a compacted- format kernel xstate area to a signal frame. Dave Hansen proposes this method to simplify

[PATCH v7 04/13] x86/xsaves: Introduce a new check that allows correct xstates copy from kernel to user directly

XSAVES is a kernel instruction and uses a compacted format. When working with user space, the kernel should provide standard-format, non-supervisor state data. We cannot do __copy_to_user() from a compacted- format kernel xstate area to a signal frame. Dave Hansen proposes this method to simplify

[PATCH v7 02/13] x86/xsaves: Rename xstate_size to fpu_kernel_xstate_size to distinguish from fpu_user_xstate_size

From: Fenghua Yu User space uses standard format xsave area. fpstate in signal frame should have standard format size. To explicitly distinguish between xstate size in kernel space and the one in user space, we rename xstate_size to fpu_kernel_xstate_size. This patch is not fixing a bug. It

[PATCH v7 01/13] x86/xsaves: Define and use fpu_user_xstate_size

From: Fenghua Yu The kernel xstate area can be in standard or compacted format; it is always in standard format for user mode. When XSAVES is enabled, the kernel uses the compacted format and it is necessary to use a separate fpu_user_xstate_size for signal/ptrace frames.

[PATCH v7 03/13] x86/xsaves: Keep init_fpstate.xsave.header.xfeatures as zero for init optimization

From: Fenghua Yu Keep init_fpstate.xsave.header.xfeatures as zero for init optimization. This is important for init optimization that is implemented in processor. If a bit corresponding to an xstate in xstate_bv is 0, it means the xstate is in init status and will not be

[PATCH v7 01/13] x86/xsaves: Define and use fpu_user_xstate_size

From: Fenghua Yu The kernel xstate area can be in standard or compacted format; it is always in standard format for user mode. When XSAVES is enabled, the kernel uses the compacted format and it is necessary to use a separate fpu_user_xstate_size for signal/ptrace frames. Signed-off-by: Fenghua

[PATCH v7 03/13] x86/xsaves: Keep init_fpstate.xsave.header.xfeatures as zero for init optimization

From: Fenghua Yu Keep init_fpstate.xsave.header.xfeatures as zero for init optimization. This is important for init optimization that is implemented in processor. If a bit corresponding to an xstate in xstate_bv is 0, it means the xstate is in init status and will not be read from memory to the

[PATCH 1/2] Create UV efi_call macros

We need a slightly different macro than the standard efi_call_virt, since those macros all assume that the function pointer, f, that gets passed in will live somewhere in efi.systab->runtime. Our EFI function pointer lives in efi.uv_systab, so we can't use the standard macros out of the box.

[PATCH 1/2] Create UV efi_call macros

We need a slightly different macro than the standard efi_call_virt, since those macros all assume that the function pointer, f, that gets passed in will live somewhere in efi.systab->runtime. Our EFI function pointer lives in efi.uv_systab, so we can't use the standard macros out of the box.

[RFC PATCH 0/2] Fix EFI runtime calls on SGI UV

These patches make the necessary changes to get SGI UVs working with the latest EFI memory mapping code. The motivation behind the changes is fairly simple: Patch 1: The current efi_call_virt macro will not work with function pointers that don't live in efi.systab->runtime Patch 2: The

[PATCH 2/2] Fix efi_call

The efi_call assembly code has a slight error that prevents us from using arguments 7 and higher, which will be passed in on the stack. mov (%rsp), %rax mov 8(%rax), %rax ... mov %rax, 40(%rsp) This code goes and grabs the return address for the current stack

[PATCH 2/2] Fix efi_call

The efi_call assembly code has a slight error that prevents us from using arguments 7 and higher, which will be passed in on the stack. mov (%rsp), %rax mov 8(%rax), %rax ... mov %rax, 40(%rsp) This code goes and grabs the return address for the current stack

[RFC PATCH 0/2] Fix EFI runtime calls on SGI UV

These patches make the necessary changes to get SGI UVs working with the latest EFI memory mapping code. The motivation behind the changes is fairly simple: Patch 1: The current efi_call_virt macro will not work with function pointers that don't live in efi.systab->runtime Patch 2: The

Re: [Patch v4 2/8] firmware: qcom: scm: Convert SCM to platform driver

On Wed 11 May 07:15 PDT 2016, Andy Gross wrote: > This patch converts the Qualcomm SCM firmware driver into a platform > driver. > > Signed-off-by: Andy Gross Acked-by: Bjorn Andersson Regards, Bjorn

Re: [Patch v4 2/8] firmware: qcom: scm: Convert SCM to platform driver

On Wed 11 May 07:15 PDT 2016, Andy Gross wrote: > This patch converts the Qualcomm SCM firmware driver into a platform > driver. > > Signed-off-by: Andy Gross Acked-by: Bjorn Andersson Regards, Bjorn

Re: [PATCH V2 13/14] dt-bindings: arm-gic: Add documentation for Tegra210 AGIC

On 11/05/16 18:28, Mark Rutland wrote: > On Wed, May 11, 2016 at 05:53:43PM +0100, Jon Hunter wrote: >> Hi Rob, Mark, >> >> On 11/05/16 17:30, Rob Herring wrote: >>> A platform driver for just gic-400 is wrong IMO until we have platform >>> drivers for all interrupt controllers. >> >> Yes, that

Re: [PATCH V2 13/14] dt-bindings: arm-gic: Add documentation for Tegra210 AGIC

On 11/05/16 18:28, Mark Rutland wrote: > On Wed, May 11, 2016 at 05:53:43PM +0100, Jon Hunter wrote: >> Hi Rob, Mark, >> >> On 11/05/16 17:30, Rob Herring wrote: >>> A platform driver for just gic-400 is wrong IMO until we have platform >>> drivers for all interrupt controllers. >> >> Yes, that

Re: [Patch v4 1/8] dt/bindings: firmware: Add Qualcomm SCM binding

On Wed 11 May 07:15 PDT 2016, Andy Gross wrote: > This patch adds the device tree support for the Qualcomm SCM firmware. > > Signed-off-by: Andy Gross > --- > .../devicetree/bindings/firmware/qcom,scm.txt | 28 > ++ > 1 file changed, 28

Re: [Patch v4 1/8] dt/bindings: firmware: Add Qualcomm SCM binding

On Wed 11 May 07:15 PDT 2016, Andy Gross wrote: > This patch adds the device tree support for the Qualcomm SCM firmware. > > Signed-off-by: Andy Gross > --- > .../devicetree/bindings/firmware/qcom,scm.txt | 28 > ++ > 1 file changed, 28 insertions(+) > create mode

[PATCH] drm/nouveau/bios: remove unused variable.

Remove unused vairable, return 0 explicitly. Signed-off-by: Muhammad Falak R Wani --- drivers/gpu/drm/nouveau/nouveau_bios.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nouveau_bios.c

[PATCH] drm/nouveau/bios: remove unused variable.

Remove unused vairable, return 0 explicitly. Signed-off-by: Muhammad Falak R Wani --- drivers/gpu/drm/nouveau/nouveau_bios.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nouveau_bios.c b/drivers/gpu/drm/nouveau/nouveau_bios.c index

[PATCH 3/3] usb: gr_udc: Remove unnecessary platform_set_drvdata().

Unnecessary [platform|pci]_set_drvdata() have been removed since the driver core clears the driver data to NULLafter device release or on probe failure. There is no need to manually clear the device driver data to NULL. Signed-off-by: Sandhya Bankar ---

[PATCH 3/3] usb: gr_udc: Remove unnecessary platform_set_drvdata().

Unnecessary [platform|pci]_set_drvdata() have been removed since the driver core clears the driver data to NULLafter device release or on probe failure. There is no need to manually clear the device driver data to NULL. Signed-off-by: Sandhya Bankar --- drivers/usb/gadget/udc/gr_udc.c | 1 -

Re: [PATCH] rpmsg: Make rpmsg sample selectable

On Wed 11 May 08:39 PDT 2016, Suman Anna wrote: > On 05/06/2016 05:15 PM, Bjorn Andersson wrote: > > On Fri 06 May 12:25 PDT 2016, Suman Anna wrote: > > > >> Hi Bjorn, > >> > >> On 05/06/2016 01:06 PM, Bjorn Andersson wrote: > >>> rpmsg is not user selectable so the rpmsg sample should not

Re: [PATCH] rpmsg: Make rpmsg sample selectable

On Wed 11 May 08:39 PDT 2016, Suman Anna wrote: > On 05/06/2016 05:15 PM, Bjorn Andersson wrote: > > On Fri 06 May 12:25 PDT 2016, Suman Anna wrote: > > > >> Hi Bjorn, > >> > >> On 05/06/2016 01:06 PM, Bjorn Andersson wrote: > >>> rpmsg is not user selectable so the rpmsg sample should not

[PATCH 2/3] usb: dwc3-keystone: Remove unnecessary platform_set_drvdata().

Unnecessary [platform|pci]_set_drvdata() have been removed since the driver core clears the driver data to NULLafter device release or on probe failure. There is no need to manually clear the device driver data to NULL Signed-off-by: Sandhya Bankar ---

[PATCH 2/3] usb: dwc3-keystone: Remove unnecessary platform_set_drvdata().

Unnecessary [platform|pci]_set_drvdata() have been removed since the driver core clears the driver data to NULLafter device release or on probe failure. There is no need to manually clear the device driver data to NULL Signed-off-by: Sandhya Bankar --- drivers/usb/dwc3/dwc3-keystone.c | 1 -

[PATCH 1/3] usb: pci: Remove unnecessary pci_set_drvdata().

Unnecessary [platform|pci]_set_drvdata() have been removed since the driver core clears the driver data to NULLafter device release or on probe failure. There is no need to manually clear the device driver data to NULL. Signed-off-by: Sandhya Bankar ---

[PATCH 1/3] usb: pci: Remove unnecessary pci_set_drvdata().

Unnecessary [platform|pci]_set_drvdata() have been removed since the driver core clears the driver data to NULLafter device release or on probe failure. There is no need to manually clear the device driver data to NULL. Signed-off-by: Sandhya Bankar --- drivers/usb/dwc2/pci.c | 1 - 1 file

Re: [RFC 2/2] perf/core: change errno for sampling event not supported in hardware

On Mon, May 09, 2016 at 10:53:43PM +0530, Vineet Gupta wrote: > Right thats what I feared. But hold on, I don't think we need to change the > ABI to > achieve what we want. Gosh why did I even take that path. > > Currently the errno switch case in perf_evsel__open_strerror() in doesn't >

Re: [RFC 2/2] perf/core: change errno for sampling event not supported in hardware

On Mon, May 09, 2016 at 10:53:43PM +0530, Vineet Gupta wrote: > Right thats what I feared. But hold on, I don't think we need to change the > ABI to > achieve what we want. Gosh why did I even take that path. > > Currently the errno switch case in perf_evsel__open_strerror() in doesn't >

[PATCH 0/3] Remove unnecessary pci_set_drvdata() and platform_set_drvdata().

Unnecessary [platform|pci]_set_drvdata() have been removed since the driver core clears the driver datato NULL after device release or on probe failure. There is no need to manually clear the device driver data to NULL. Sandhya Bankar (3): usb: pci: Remove unnecessary pci_set_drvdata().

[PATCH 0/3] Remove unnecessary pci_set_drvdata() and platform_set_drvdata().

Unnecessary [platform|pci]_set_drvdata() have been removed since the driver core clears the driver datato NULL after device release or on probe failure. There is no need to manually clear the device driver data to NULL. Sandhya Bankar (3): usb: pci: Remove unnecessary pci_set_drvdata().

Re: [PATCH 06/10] watchdog: ebc-c384_wdt: Utilize the ISA bus driver

t;Modules linked in: >CPU: 1 PID: 1 Comm: swapper/0 Not tainted >4.6.0-rc7-next-20160511-sasha-00024-g13dfe33 #3081 >task: 88005b2f8000 ti: 88005b30 task.ti: 88005b30 >RIP: driver_register (drivers/base/driver.c:153 (discriminator 1)) >RSP: :8

Re: [PATCH 06/10] watchdog: ebc-c384_wdt: Utilize the ISA bus driver

er for the WinSystems EBC-C384 watchdog timer driver. >> >> Signed-off-by: William Breathitt Gray > >Hey William, > >I'm seeing this on boot: > >kernel BUG at drivers/base/driver.c:153! >invalid opcode: [#1] PREEMPT SMP KASAN >Modules linked in: >CPU: 1

Re: [PATCH 20/25] arm64:ilp32: add sys_ilp32.c and a separate table (in entry.S) to use it

On Wednesday 11 May 2016 17:59:01 Catalin Marinas wrote: > On Wed, May 11, 2016 at 12:55:01PM +0200, Arnd Bergmann wrote: > > On Wednesday 11 May 2016 11:04:38 Yury Norov wrote: > > > On Wed, May 11, 2016 at 10:04:16AM +0800, Zhangjian (Bamvor) wrote: > > > [...] > > > > > > > >>Ok, I will test

Re: [PATCH 20/25] arm64:ilp32: add sys_ilp32.c and a separate table (in entry.S) to use it

On Wednesday 11 May 2016 17:59:01 Catalin Marinas wrote: > On Wed, May 11, 2016 at 12:55:01PM +0200, Arnd Bergmann wrote: > > On Wednesday 11 May 2016 11:04:38 Yury Norov wrote: > > > On Wed, May 11, 2016 at 10:04:16AM +0800, Zhangjian (Bamvor) wrote: > > > [...] > > > > > > > >>Ok, I will test

Re: [PATCH v2 6/6] drm: Add helper for simple display pipeline

Den 11.05.2016 21:10, skrev Paul Bolle: On wo, 2016-05-11 at 19:09 +0200, Daniel Vetter wrote: On Wed, May 11, 2016 at 06:09:22PM +0200, Noralf Trønnes wrote: --- a/drivers/gpu/drm/Kconfig +++ b/drivers/gpu/drm/Kconfig +config DRM_SIMPLE_KMS_HELPER + tristate + depends on DRM +

Re: [PATCH v2 6/6] drm: Add helper for simple display pipeline

Den 11.05.2016 21:10, skrev Paul Bolle: On wo, 2016-05-11 at 19:09 +0200, Daniel Vetter wrote: On Wed, May 11, 2016 at 06:09:22PM +0200, Noralf Trønnes wrote: --- a/drivers/gpu/drm/Kconfig +++ b/drivers/gpu/drm/Kconfig +config DRM_SIMPLE_KMS_HELPER + tristate + depends on DRM +

Fw: [GIT] Networking

Sorry, forgot to CC: the lists on the initial send. --- Begin Message --- Hopefully the last round of fixes this release, fingers crossed :) 1) Initialize static nf_conntrack_locks_all_lock properly, from Florian Westphal. 2) Need to cancel pending work when destroying IDLETIMER entries,

Fw: [GIT] Networking

Sorry, forgot to CC: the lists on the initial send. --- Begin Message --- Hopefully the last round of fixes this release, fingers crossed :) 1) Initialize static nf_conntrack_locks_all_lock properly, from Florian Westphal. 2) Need to cancel pending work when destroying IDLETIMER entries,

[PATCH] crypto: qat: remove unused vairable.

Remove the unused variable ret, and return 0 explicitly. Signed-off-by: Muhammad Falak R Wani --- drivers/crypto/qat/qat_common/adf_ctl_drv.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/crypto/qat/qat_common/adf_ctl_drv.c

[PATCH] crypto: qat: remove unused vairable.

Remove the unused variable ret, and return 0 explicitly. Signed-off-by: Muhammad Falak R Wani --- drivers/crypto/qat/qat_common/adf_ctl_drv.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/crypto/qat/qat_common/adf_ctl_drv.c

4.1.24-stable: iwlwifi patch applied to wrong file

Hi again, in 4.1.24-stable commit fdfdfc7cdf (iwlwifi: pcie: lower the debug level for RSA semaphore access) was applied to the wrong file. It patched drivers/net/wireless/intel/iwlwifi/pcie/trans.c whereas it should have patched drivers/net/wireless/iwlwifi/pcie/trans.c instead.

4.1.24-stable: iwlwifi patch applied to wrong file

Hi again, in 4.1.24-stable commit fdfdfc7cdf (iwlwifi: pcie: lower the debug level for RSA semaphore access) was applied to the wrong file. It patched drivers/net/wireless/intel/iwlwifi/pcie/trans.c whereas it should have patched drivers/net/wireless/iwlwifi/pcie/trans.c instead.

Re: [PATCH v2 6/6] drm: Add helper for simple display pipeline

Den 11.05.2016 19:09, skrev Daniel Vetter: On Wed, May 11, 2016 at 06:09:22PM +0200, Noralf Trønnes wrote: Provides helper functions for drivers that have a simple display pipeline. Plane, crtc and encoder are collapsed into one entity. Signed-off-by: Noralf Trønnes Looks

Re: [PATCH v2 6/6] drm: Add helper for simple display pipeline

Den 11.05.2016 19:09, skrev Daniel Vetter: On Wed, May 11, 2016 at 06:09:22PM +0200, Noralf Trønnes wrote: Provides helper functions for drivers that have a simple display pipeline. Plane, crtc and encoder are collapsed into one entity. Signed-off-by: Noralf Trønnes Looks really nice, just a

Re: [PATCH 2/3] memory-hotplug: more general validation of zone during online

On Wed, May 11, 2016 at 08:17:41AM -0700, Yasuaki Ishimatsu wrote: On Tue, 10 May 2016 15:39:43 -0500 Reza Arbab wrote: + if (idx < target) { + /* pages must be at end of current zone */ + if (pfn + nr_pages != zone_end_pfn(zone)) +

Re: [PATCH 2/3] memory-hotplug: more general validation of zone during online

On Wed, May 11, 2016 at 08:17:41AM -0700, Yasuaki Ishimatsu wrote: On Tue, 10 May 2016 15:39:43 -0500 Reza Arbab wrote: + if (idx < target) { + /* pages must be at end of current zone */ + if (pfn + nr_pages != zone_end_pfn(zone)) +

[PATCH] irqchip/gic-v3: fix quiescence check in gic_enable_redist

Signed-off-by: Andrew Jones --- I'm unaware of any problems this may have caused. I only just saw it while reading over the code. drivers/irqchip/irq-gic-v3.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/irqchip/irq-gic-v3.c

[PATCH] irqchip/gic-v3: fix quiescence check in gic_enable_redist

Signed-off-by: Andrew Jones --- I'm unaware of any problems this may have caused. I only just saw it while reading over the code. drivers/irqchip/irq-gic-v3.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/irqchip/irq-gic-v3.c b/drivers/irqchip/irq-gic-v3.c index

Re: [PATCH 00/12] TLB/XPA fixes & cleanups

On 05/11/2016 03:03 AM, Ralf Baechle wrote: > On Tue, May 10, 2016 at 10:47:48AM -0700, Florian Fainelli wrote: > >>> Applied - but "MIPS: Separate XPA CPU feature into LPA and MVH" causes >>> a massive conflict with Florian's RIXI patches >>> >>> [3/6] MIPS: Allow RIXI to be used on non-R2 or

Re: [PATCH 00/12] TLB/XPA fixes & cleanups

On 05/11/2016 03:03 AM, Ralf Baechle wrote: > On Tue, May 10, 2016 at 10:47:48AM -0700, Florian Fainelli wrote: > >>> Applied - but "MIPS: Separate XPA CPU feature into LPA and MVH" causes >>> a massive conflict with Florian's RIXI patches >>> >>> [3/6] MIPS: Allow RIXI to be used on non-R2 or

Re: [PATCH 0/2] ARM: dts: sunxi: Add display clocks to sun[47]i.dtsi

On Tue, May 10, 2016 at 10:24:05PM +0300, Priit Laes wrote: > Enable the display and TCON clocks that are needed to drive the display > engine, tcon and TV encoders. > > Please note that currently the parent handling for clocks using > 'allwinner,sun4i-a10-display-clk' compatible with number of

Re: [PATCH 0/2] ARM: dts: sunxi: Add display clocks to sun[47]i.dtsi

On Tue, May 10, 2016 at 10:24:05PM +0300, Priit Laes wrote: > Enable the display and TCON clocks that are needed to drive the display > engine, tcon and TV encoders. > > Please note that currently the parent handling for clocks using > 'allwinner,sun4i-a10-display-clk' compatible with number of

Re: [RFC PATCH 8/8] KEYS: Implement PKCS#8 RSA Private Key parser [ver 3]

On Wed, 2016-05-11 at 15:22 +0100, David Howells wrote: > Implement PKCS#8 RSA Private Key format [RFC 5208] parser for the > asymmetric key type.  For the moment, this will only support unencrypted > DER blobs.  PEM and decryption can be added later. I would recommend *not* adding PEM and

Re: [RFC PATCH 8/8] KEYS: Implement PKCS#8 RSA Private Key parser [ver 3]

On Wed, 2016-05-11 at 15:22 +0100, David Howells wrote: > Implement PKCS#8 RSA Private Key format [RFC 5208] parser for the > asymmetric key type.  For the moment, this will only support unencrypted > DER blobs.  PEM and decryption can be added later. I would recommend *not* adding PEM and

Re: [PATCH v2 6/6] drm: Add helper for simple display pipeline

On wo, 2016-05-11 at 19:09 +0200, Daniel Vetter wrote: > On Wed, May 11, 2016 at 06:09:22PM +0200, Noralf Trønnes wrote: > > --- a/drivers/gpu/drm/Kconfig > > +++ b/drivers/gpu/drm/Kconfig > > +config DRM_SIMPLE_KMS_HELPER > > + tristate > > + depends on DRM > > + select DRM_KMS_HELPER > >

Re: [PATCH v2 6/6] drm: Add helper for simple display pipeline

On wo, 2016-05-11 at 19:09 +0200, Daniel Vetter wrote: > On Wed, May 11, 2016 at 06:09:22PM +0200, Noralf Trønnes wrote: > > --- a/drivers/gpu/drm/Kconfig > > +++ b/drivers/gpu/drm/Kconfig > > +config DRM_SIMPLE_KMS_HELPER > > + tristate > > + depends on DRM > > + select DRM_KMS_HELPER > >

Re: [PATH v2] NVMe: init nvme queue before enabling irq

On Wed, May 11, 2016 at 11:25:16AM +0200, Johannes Thumshirn wrote: > What ever happened to this patch? > I can easily reproduce the bug using > while [ true ]; do rmmod nvme nvme_core; modprobe nvme; done This patch was supposed to fix using a doorbell between resets when the driver had BAR0

Re: [PATH v2] NVMe: init nvme queue before enabling irq

On Wed, May 11, 2016 at 11:25:16AM +0200, Johannes Thumshirn wrote: > What ever happened to this patch? > I can easily reproduce the bug using > while [ true ]; do rmmod nvme nvme_core; modprobe nvme; done This patch was supposed to fix using a doorbell between resets when the driver had BAR0

[PATCH] tools lib traceevent: Do not reassign parg after collapse_tree()

At the end of process_filter(), collapse_tree() was changed to update the parg parameter, but the reassignment after the call wasn't removed. What happens is that the "current_op" gets modified and freed and parg is assigned to the new allocated argument. But after the call to collapse_tree(),

[PATCH] tools lib traceevent: Do not reassign parg after collapse_tree()

At the end of process_filter(), collapse_tree() was changed to update the parg parameter, but the reassignment after the call wasn't removed. What happens is that the "current_op" gets modified and freed and parg is assigned to the new allocated argument. But after the call to collapse_tree(),

[PATCH] tracing: Expose CPU physical addresses (resource values) for PCI devices

Previously, mmio_print_pcidev() put "user" addresses in the trace buffer. On most architectures, these are the same as CPU physical addresses, but on microblaze, mips, powerpc, and sparc, they may be something else, typically a raw BAR value (a bus address as opposed to a CPU address). Always

[PATCH] tracing: Expose CPU physical addresses (resource values) for PCI devices

Previously, mmio_print_pcidev() put "user" addresses in the trace buffer. On most architectures, these are the same as CPU physical addresses, but on microblaze, mips, powerpc, and sparc, they may be something else, typically a raw BAR value (a bus address as opposed to a CPU address). Always

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