Re: 9f4835fb96 ("x86/fpu: Tighten validation of user-supplied .."): Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

* kernel test robot wrote: > Greetings, > > 0day kernel testing robot got the below dmesg and the first bad commit is > > https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/fpu > > commit 9f4835fb965d8eea7e608d0cb62c246c804dec90 > Author: Eric

Re: 9f4835fb96 ("x86/fpu: Tighten validation of user-supplied .."): Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

* kernel test robot wrote: > Greetings, > > 0day kernel testing robot got the below dmesg and the first bad commit is > > https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/fpu > > commit 9f4835fb965d8eea7e608d0cb62c246c804dec90 > Author: Eric Biggers > AuthorDate: Fri

[tip:x86/asm] x86/asm: Remove unnecessary \n\t in front of CC_SET() from asm templates

Commit-ID: 3c52b5c64326d9dcfee4e10611c53ec1b1b20675 Gitweb: http://git.kernel.org/tip/3c52b5c64326d9dcfee4e10611c53ec1b1b20675 Author: Uros Bizjak AuthorDate: Wed, 6 Sep 2017 17:18:08 +0200 Committer: Ingo Molnar CommitDate: Sun, 24 Sep 2017

[tip:x86/asm] x86/asm: Remove unnecessary \n\t in front of CC_SET() from asm templates

Commit-ID: 3c52b5c64326d9dcfee4e10611c53ec1b1b20675 Gitweb: http://git.kernel.org/tip/3c52b5c64326d9dcfee4e10611c53ec1b1b20675 Author: Uros Bizjak AuthorDate: Wed, 6 Sep 2017 17:18:08 +0200 Committer: Ingo Molnar CommitDate: Sun, 24 Sep 2017 11:19:01 +0200 x86/asm: Remove unnecessary

[PATCH 01/10] x86/fpu: Introduce validate_xstate_header()

From: Eric Biggers Move validation of user-supplied xstate_header into a helper function, in preparation of calling it from both the ptrace and sigreturn syscall paths. The new function also considers it to be an error if *any* reserved bits are set, whereas before we were

[PATCH 01/10] x86/fpu: Introduce validate_xstate_header()

From: Eric Biggers Move validation of user-supplied xstate_header into a helper function, in preparation of calling it from both the ptrace and sigreturn syscall paths. The new function also considers it to be an error if *any* reserved bits are set, whereas before we were just clearing most of

[PATCH 03/10] x86/fpu: Use validate_xstate_header() to validate the xstate_header in sanitize_restored_xstate()

From: Eric Biggers Tighten the checks in sanitize_restored_xstate(). Signed-off-by: Eric Biggers Cc: Andy Lutomirski Cc: Dave Hansen Cc: Dmitry Vyukov Cc: Fenghua Yu

[PATCH 03/10] x86/fpu: Use validate_xstate_header() to validate the xstate_header in sanitize_restored_xstate()

From: Eric Biggers Tighten the checks in sanitize_restored_xstate(). Signed-off-by: Eric Biggers Cc: Andy Lutomirski Cc: Dave Hansen Cc: Dmitry Vyukov Cc: Fenghua Yu Cc: Kees Cook Cc: Kevin Hao Cc: Linus Torvalds Cc: Michael Halcrow Cc: Oleg Nesterov Cc: Peter Zijlstra Cc: Rik van

[PATCH 04/10] x86/fpu: Copy the full state_header in copy_kernel_to_xstate()

From: Eric Biggers This is in preparation to verify the full xstate header as supplied by user-space. Signed-off-by: Eric Biggers Cc: Andy Lutomirski Cc: Dave Hansen Cc: Dmitry Vyukov

[PATCH 04/10] x86/fpu: Copy the full state_header in copy_kernel_to_xstate()

From: Eric Biggers This is in preparation to verify the full xstate header as supplied by user-space. Signed-off-by: Eric Biggers Cc: Andy Lutomirski Cc: Dave Hansen Cc: Dmitry Vyukov Cc: Fenghua Yu Cc: Kees Cook Cc: Kevin Hao Cc: Linus Torvalds Cc: Michael Halcrow Cc: Oleg Nesterov

[PATCH 07/10] x86/fpu: Copy the full header in copy_user_to_xstate()

From: Eric Biggers This is in preparation to verify the full xstate header as supplied by user-space. Signed-off-by: Eric Biggers Cc: Andy Lutomirski Cc: Dave Hansen Cc: Dmitry Vyukov

[PATCH 07/10] x86/fpu: Copy the full header in copy_user_to_xstate()

From: Eric Biggers This is in preparation to verify the full xstate header as supplied by user-space. Signed-off-by: Eric Biggers Cc: Andy Lutomirski Cc: Dave Hansen Cc: Dmitry Vyukov Cc: Fenghua Yu Cc: Kees Cook Cc: Kevin Hao Cc: Linus Torvalds Cc: Michael Halcrow Cc: Oleg Nesterov

[PATCH 06/10] x86/fpu: Use validate_xstate_header() to validate the xstate_header in copy_kernel_to_xstate()

From: Eric Biggers Tighten the checks in copy_kernel_to_xstate(). Signed-off-by: Eric Biggers Cc: Andy Lutomirski Cc: Dave Hansen Cc: Dmitry Vyukov Cc: Fenghua Yu

[PATCH 06/10] x86/fpu: Use validate_xstate_header() to validate the xstate_header in copy_kernel_to_xstate()

From: Eric Biggers Tighten the checks in copy_kernel_to_xstate(). Signed-off-by: Eric Biggers Cc: Andy Lutomirski Cc: Dave Hansen Cc: Dmitry Vyukov Cc: Fenghua Yu Cc: Kees Cook Cc: Kevin Hao Cc: Linus Torvalds Cc: Michael Halcrow Cc: Oleg Nesterov Cc: Peter Zijlstra Cc: Rik van Riel

[PATCH 08/10] x86/fpu: Eliminate the 'xfeatures' local variable in copy_user_to_xstate()

From: Eric Biggers We now have this field in hdr.xfeatures. Signed-off-by: Eric Biggers Cc: Andy Lutomirski Cc: Dave Hansen Cc: Dmitry Vyukov Cc: Fenghua Yu Cc:

[PATCH 08/10] x86/fpu: Eliminate the 'xfeatures' local variable in copy_user_to_xstate()

From: Eric Biggers We now have this field in hdr.xfeatures. Signed-off-by: Eric Biggers Cc: Andy Lutomirski Cc: Dave Hansen Cc: Dmitry Vyukov Cc: Fenghua Yu Cc: Kees Cook Cc: Kevin Hao Cc: Linus Torvalds Cc: Michael Halcrow Cc: Oleg Nesterov Cc: Peter Zijlstra Cc: Rik van Riel Cc:

[PATCH v3 2/5] mtd: spi-nor: cadence-quadspi: add a delay in write sequence

As per 66AK2G02 TRM[1] SPRUHY8F section 11.15.5.3 Indirect Access Controller programming sequence, a delay equal to couple of QSPI master clock(~5ns) is required after setting CQSPI_REG_INDIRECTWR_START bit and writing data to the flash. Introduce a quirk flag CQSPI_NEEDS_WR_DELAY to handle this

[PATCH v3 2/5] mtd: spi-nor: cadence-quadspi: add a delay in write sequence

As per 66AK2G02 TRM[1] SPRUHY8F section 11.15.5.3 Indirect Access Controller programming sequence, a delay equal to couple of QSPI master clock(~5ns) is required after setting CQSPI_REG_INDIRECTWR_START bit and writing data to the flash. Introduce a quirk flag CQSPI_NEEDS_WR_DELAY to handle this

[PATCH v3 0/5] K2G: Add QSPI support

This series adds support for Cadence QSPI IP present in TI's 66AK2G SoC. The patches enhance the existing cadence-quadspi driver to support loopback clock circuit, pm_runtime support and tweaks for 66AK2G SoC. Change log: v3: * Fix build warnings reported by kbuild test bot. Resend: * Rebase to

[PATCH v3 0/5] K2G: Add QSPI support

This series adds support for Cadence QSPI IP present in TI's 66AK2G SoC. The patches enhance the existing cadence-quadspi driver to support loopback clock circuit, pm_runtime support and tweaks for 66AK2G SoC. Change log: v3: * Fix build warnings reported by kbuild test bot. Resend: * Rebase to

[PATCH v3 3/5] mtd: spi-nor: cadence-quadspi: Add new binding to enable loop-back circuit

Cadence QSPI IP has a adapted loop-back circuit which can be enabled by setting BYPASS field to 0 in READCAPTURE register. It enables use of QSPI return clock to latch the data rather than the internal QSPI reference clock. For high speed operations, adapted loop-back circuit using QSPI return

[PATCH v3 4/5] mtd: spi-nor: cadence-quadspi: Add support to enable loop-back clock circuit

Cadence QSPI IP has a adapted loop-back circuit which can be enabled by setting BYPASS field to 0 in READCAPTURE register. It enables use of QSPI return clock to latch the data rather than the internal QSPI reference clock. For high speed operations, adapted loop-back circuit using QSPI return

[PATCH v3 3/5] mtd: spi-nor: cadence-quadspi: Add new binding to enable loop-back circuit

Cadence QSPI IP has a adapted loop-back circuit which can be enabled by setting BYPASS field to 0 in READCAPTURE register. It enables use of QSPI return clock to latch the data rather than the internal QSPI reference clock. For high speed operations, adapted loop-back circuit using QSPI return

[PATCH v3 4/5] mtd: spi-nor: cadence-quadspi: Add support to enable loop-back clock circuit

Cadence QSPI IP has a adapted loop-back circuit which can be enabled by setting BYPASS field to 0 in READCAPTURE register. It enables use of QSPI return clock to latch the data rather than the internal QSPI reference clock. For high speed operations, adapted loop-back circuit using QSPI return

[PATCH v3 5/5] mtd: spi-nor: cadence-quadspi: Add runtime PM support

Add pm_runtime* calls to cadence-quadspi driver. This is required to switch on QSPI power domain on TI 66AK2G SoC during probe. Signed-off-by: Vignesh R --- drivers/mtd/spi-nor/cadence-quadspi.c | 11 +++ 1 file changed, 11 insertions(+) diff --git

[PATCH v3 5/5] mtd: spi-nor: cadence-quadspi: Add runtime PM support

Add pm_runtime* calls to cadence-quadspi driver. This is required to switch on QSPI power domain on TI 66AK2G SoC during probe. Signed-off-by: Vignesh R --- drivers/mtd/spi-nor/cadence-quadspi.c | 11 +++ 1 file changed, 11 insertions(+) diff --git

[PATCH v3 1/5] mtd: spi-nor: cadence-quadspi: Add TI 66AK2G SoC specific compatible

Update binding documentation to add a new compatible for TI 66AK2G SoC, to handle TI SoC specific quirks in the driver. Signed-off-by: Vignesh R Acked-by: Rob Herring --- Documentation/devicetree/bindings/mtd/cadence-quadspi.txt | 4 +++- 1 file changed, 3

[PATCH 10/10] x86/fpu: Use using_compacted_format() instead of open coded X86_FEATURE_XSAVES

From: Eric Biggers Signed-off-by: Eric Biggers Cc: Andy Lutomirski Cc: Dave Hansen Cc: Dmitry Vyukov Cc: Fenghua Yu Cc: Kees Cook Cc:

[PATCH v3 1/5] mtd: spi-nor: cadence-quadspi: Add TI 66AK2G SoC specific compatible

Update binding documentation to add a new compatible for TI 66AK2G SoC, to handle TI SoC specific quirks in the driver. Signed-off-by: Vignesh R Acked-by: Rob Herring --- Documentation/devicetree/bindings/mtd/cadence-quadspi.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff

[PATCH 10/10] x86/fpu: Use using_compacted_format() instead of open coded X86_FEATURE_XSAVES

From: Eric Biggers Signed-off-by: Eric Biggers Cc: Andy Lutomirski Cc: Dave Hansen Cc: Dmitry Vyukov Cc: Fenghua Yu Cc: Kees Cook Cc: Kevin Hao Cc: Linus Torvalds Cc: Michael Halcrow Cc: Oleg Nesterov Cc: Peter Zijlstra Cc: Rik van Riel Cc: Thomas Gleixner Cc: Wanpeng Li Cc:

[PATCH 05/10] x86/fpu: Eliminate the 'xfeatures' local variable in copy_kernel_to_xstate()

From: Eric Biggers We have this information in the xstate_header. Signed-off-by: Eric Biggers Cc: Andy Lutomirski Cc: Dave Hansen Cc: Dmitry Vyukov Cc: Fenghua Yu

[PATCH 05/10] x86/fpu: Eliminate the 'xfeatures' local variable in copy_kernel_to_xstate()

From: Eric Biggers We have this information in the xstate_header. Signed-off-by: Eric Biggers Cc: Andy Lutomirski Cc: Dave Hansen Cc: Dmitry Vyukov Cc: Fenghua Yu Cc: Kees Cook Cc: Kevin Hao Cc: Linus Torvalds Cc: Michael Halcrow Cc: Oleg Nesterov Cc: Peter Zijlstra Cc: Rik van Riel

[PATCH 09/10] x86/fpu: Use validate_xstate_header() to validate the xstate_header in copy_user_to_xstate()

From: Eric Biggers Tighten the checks in copy_user_to_xstate(). Signed-off-by: Eric Biggers Cc: Andy Lutomirski Cc: Dave Hansen Cc: Dmitry Vyukov Cc: Fenghua Yu

[PATCH 02/10] x86/fpu: Use validate_xstate_header() to validate the xstate_header in xstateregs_set()

From: Eric Biggers Tighten the checks in xstateregs_set(). Signed-off-by: Eric Biggers Cc: Andy Lutomirski Cc: Dave Hansen Cc: Dmitry Vyukov Cc: Fenghua Yu Cc:

[PATCH 00/10] x86/fpu: Split up "x86/fpu: Tighten validation of user-supplied xstate_header"

As mentioned before, the patch was too big and too complex, and I've split it up into 10 smaller, bisectable patches: Eric Biggers (10): x86/fpu: Introduce validate_xstate_header() x86/fpu: Use validate_xstate_header() to validate the xstate_header in xstateregs_set() x86/fpu: Use

[PATCH 09/10] x86/fpu: Use validate_xstate_header() to validate the xstate_header in copy_user_to_xstate()

From: Eric Biggers Tighten the checks in copy_user_to_xstate(). Signed-off-by: Eric Biggers Cc: Andy Lutomirski Cc: Dave Hansen Cc: Dmitry Vyukov Cc: Fenghua Yu Cc: Kees Cook Cc: Kevin Hao Cc: Linus Torvalds Cc: Michael Halcrow Cc: Oleg Nesterov Cc: Peter Zijlstra Cc: Rik van Riel

[PATCH 02/10] x86/fpu: Use validate_xstate_header() to validate the xstate_header in xstateregs_set()

From: Eric Biggers Tighten the checks in xstateregs_set(). Signed-off-by: Eric Biggers Cc: Andy Lutomirski Cc: Dave Hansen Cc: Dmitry Vyukov Cc: Fenghua Yu Cc: Kees Cook Cc: Kevin Hao Cc: Linus Torvalds Cc: Michael Halcrow Cc: Oleg Nesterov Cc: Peter Zijlstra Cc: Rik van Riel Cc:

[PATCH 00/10] x86/fpu: Split up "x86/fpu: Tighten validation of user-supplied xstate_header"

As mentioned before, the patch was too big and too complex, and I've split it up into 10 smaller, bisectable patches: Eric Biggers (10): x86/fpu: Introduce validate_xstate_header() x86/fpu: Use validate_xstate_header() to validate the xstate_header in xstateregs_set() x86/fpu: Use

[PATCH] rpmsg: Allow RPMSG_VIRTIO to be enabled via menuconfig or defconfig

Currently, RPMSG_VIRTIO can only be enabled if some other kconfig option selects it. This does not allow it to be enabled for virtualized systems where Virtio RPMSG is available over Virtio MMIO or PCI transport. This patch updates RPMSG_VIRTIO kconfig option so that we can enable the VirtIO

[PATCH] rpmsg: Allow RPMSG_VIRTIO to be enabled via menuconfig or defconfig

Currently, RPMSG_VIRTIO can only be enabled if some other kconfig option selects it. This does not allow it to be enabled for virtualized systems where Virtio RPMSG is available over Virtio MMIO or PCI transport. This patch updates RPMSG_VIRTIO kconfig option so that we can enable the VirtIO

Re: [PATCH 1/6] [media] omap_vout: Delete an error message for a failed memory allocation in omap_vout_create_video_devices()

On Sun, 2017-09-24 at 12:22 +0200, SF Markus Elfring wrote: > Omit an extra message for a memory allocation failure in this function. [] > diff --git a/drivers/media/platform/omap/omap_vout.c > b/drivers/media/platform/omap/omap_vout.c [] > @@ -1948,7 +1948,5 @@ static int __init

Re: [PATCH 1/6] [media] omap_vout: Delete an error message for a failed memory allocation in omap_vout_create_video_devices()

On Sun, 2017-09-24 at 12:22 +0200, SF Markus Elfring wrote: > Omit an extra message for a memory allocation failure in this function. [] > diff --git a/drivers/media/platform/omap/omap_vout.c > b/drivers/media/platform/omap/omap_vout.c [] > @@ -1948,7 +1948,5 @@ static int __init

[PATCH 6/6] [media] omap_vout: Delete two unnecessary variable initialisations in omap_vout_probe()

From: Markus Elfring Date: Sun, 24 Sep 2017 11:33:39 +0200 The variables "dssdev" and "vid_dev" will eventually be set to appropriate pointers a bit later. Thus omit the explicit initialisations at the beginning. Signed-off-by: Markus Elfring

[PATCH 6/6] [media] omap_vout: Delete two unnecessary variable initialisations in omap_vout_probe()

From: Markus Elfring Date: Sun, 24 Sep 2017 11:33:39 +0200 The variables "dssdev" and "vid_dev" will eventually be set to appropriate pointers a bit later. Thus omit the explicit initialisations at the beginning. Signed-off-by: Markus Elfring --- drivers/media/platform/omap/omap_vout.c | 4

[PATCH 5/6] [media] omap_vout: Delete an unnecessary variable initialisation in omap_vout_open()

From: Markus Elfring Date: Sun, 24 Sep 2017 11:20:11 +0200 The local variable "vout" is reassigned by a statement at the beginning. Thus omit the explicit initialisation. Signed-off-by: Markus Elfring ---

[PATCH 5/6] [media] omap_vout: Delete an unnecessary variable initialisation in omap_vout_open()

From: Markus Elfring Date: Sun, 24 Sep 2017 11:20:11 +0200 The local variable "vout" is reassigned by a statement at the beginning. Thus omit the explicit initialisation. Signed-off-by: Markus Elfring --- drivers/media/platform/omap/omap_vout.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH 4/6] [media] omap_vout: Fix a possible null pointer dereference in omap_vout_open()

From: Markus Elfring Date: Sun, 24 Sep 2017 11:00:57 +0200 Move a debug message so that a null pointer access can not happen for the variable "vout" in this function. Fixes: 5c7ab6348e7b3fcca2b8ee548306c774472971e2 ("V4L/DVB: V4L2: Add support for OMAP2/3 V4L2

[PATCH 4/6] [media] omap_vout: Fix a possible null pointer dereference in omap_vout_open()

From: Markus Elfring Date: Sun, 24 Sep 2017 11:00:57 +0200 Move a debug message so that a null pointer access can not happen for the variable "vout" in this function. Fixes: 5c7ab6348e7b3fcca2b8ee548306c774472971e2 ("V4L/DVB: V4L2: Add support for OMAP2/3 V4L2 display driver on top of DSS2")

[PATCH 3/6] [media] omap_vout: Adjust a null pointer check in two functions

From: Markus Elfring Date: Sun, 24 Sep 2017 10:30:29 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The script “checkpatch.pl” pointed information out like the following. Comparison to NULL could be written !… Thus

[PATCH 3/6] [media] omap_vout: Adjust a null pointer check in two functions

From: Markus Elfring Date: Sun, 24 Sep 2017 10:30:29 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The script “checkpatch.pl” pointed information out like the following. Comparison to NULL could be written !… Thus fix the affected source code

radeon_get_bios: BUG: unable to handle kernel paging request

Hi, while trying to resurrect my old Macbook as an 32 bit kernel testing device, I think someone broke the radeon driver on this first generation pure EFI boot Macbook. My guess would be that the introduction of the vga_switcheroo code did break the radeon_get_bios functionality. I will try

radeon_get_bios: BUG: unable to handle kernel paging request

Hi, while trying to resurrect my old Macbook as an 32 bit kernel testing device, I think someone broke the radeon driver on this first generation pure EFI boot Macbook. My guess would be that the introduction of the vga_switcheroo code did break the radeon_get_bios functionality. I will try

[PATCH 2/6] [media] omap_vout: Improve a size determination in two functions

From: Markus Elfring Date: Sun, 24 Sep 2017 10:18:26 +0200 Replace the specification of data structures by variable references as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

[PATCH 2/6] [media] omap_vout: Improve a size determination in two functions

From: Markus Elfring Date: Sun, 24 Sep 2017 10:18:26 +0200 Replace the specification of data structures by variable references as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style convention. This issue was

[PATCH 1/6] [media] omap_vout: Delete an error message for a failed memory allocation in omap_vout_create_video_devices()

From: Markus Elfring Date: Sun, 24 Sep 2017 10:08:22 +0200 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH 1/6] [media] omap_vout: Delete an error message for a failed memory allocation in omap_vout_create_video_devices()

From: Markus Elfring Date: Sun, 24 Sep 2017 10:08:22 +0200 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- drivers/media/platform/omap/omap_vout.c | 4 +--- 1 file changed, 1

[PATCH 0/6] [media] omap_vout: Adjustments for three function implementations

From: Markus Elfring Date: Sun, 24 Sep 2017 12:06:54 +0200 A few update suggestions were taken into account from static source code analysis. Markus Elfring (6): Delete an error message for a failed memory allocation in omap_vout_create_video_devices()

[PATCH 0/6] [media] omap_vout: Adjustments for three function implementations

From: Markus Elfring Date: Sun, 24 Sep 2017 12:06:54 +0200 A few update suggestions were taken into account from static source code analysis. Markus Elfring (6): Delete an error message for a failed memory allocation in omap_vout_create_video_devices() Improve a size determination in two

Re: [PATCH] sparc64: mmu_context: Add missing include files

On Sun, Sep 10, 2017 at 11:44 PM, Guenter Roeck wrote: > Fix the following build errors. > > In file included from arch/sparc/include/asm/mmu_context.h:4:0, > from include/linux/mmu_context.h:4, > from

Re: [PATCH] sparc64: mmu_context: Add missing include files

On Sun, Sep 10, 2017 at 11:44 PM, Guenter Roeck wrote: > Fix the following build errors. > > In file included from arch/sparc/include/asm/mmu_context.h:4:0, > from include/linux/mmu_context.h:4, > from drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.h:29, >

Re: 9f4835fb96 ("x86/fpu: Tighten validation of user-supplied .."): Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

* kernel test robot wrote: > Greetings, > > 0day kernel testing robot got the below dmesg and the first bad commit is > > https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/fpu > > commit 9f4835fb965d8eea7e608d0cb62c246c804dec90 > Author: Eric

Re: 9f4835fb96 ("x86/fpu: Tighten validation of user-supplied .."): Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

* kernel test robot wrote: > Greetings, > > 0day kernel testing robot got the below dmesg and the first bad commit is > > https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/fpu > > commit 9f4835fb965d8eea7e608d0cb62c246c804dec90 > Author: Eric Biggers > AuthorDate: Fri

Re: [PATCH] firmware: dmi_scan: Drop dmi_initialized

* Jean Delvare wrote: > Hi Ingo, > > On Sat, 23 Sep 2017 12:50:31 +0200, Ingo Molnar wrote: > > * Jean Delvare wrote: > > > > > I don't think it makes sense to check for a possible bad > > > initialization order at run time on every system when it is all >

Re: [PATCH] firmware: dmi_scan: Drop dmi_initialized

* Jean Delvare wrote: > Hi Ingo, > > On Sat, 23 Sep 2017 12:50:31 +0200, Ingo Molnar wrote: > > * Jean Delvare wrote: > > > > > I don't think it makes sense to check for a possible bad > > > initialization order at run time on every system when it is all > > > decided at build time. > > > >

[char-misc 1/2] mei: always use domain runtime pm callbacks.

From: Alexander Usyskin This patch fixes a regression caused by the new changes in the run wake handlers, pci_dev_run_wake() return true when wake is possible from the software perspective not whether it is actually enabled. The mei devices that support D0i3 are no

[char-misc 1/2] mei: always use domain runtime pm callbacks.

From: Alexander Usyskin This patch fixes a regression caused by the new changes in the run wake handlers, pci_dev_run_wake() return true when wake is possible from the software perspective not whether it is actually enabled. The mei devices that support D0i3 are no longer receiving an interrupt

[char-misc 0/2] mei updates for 4.14-rc2

Hello Greg, here are updates for 4.14-rc2 containing: A regression fix that hit us in 4.13, unfortunately we haven't spotted it during the 4.13 cycle. A new device id, for Gemini Lake SoC. This particular patch doesn't apply cleanly to stable kernels so I will post separated backport patches

[char-misc 0/2] mei updates for 4.14-rc2

Hello Greg, here are updates for 4.14-rc2 containing: A regression fix that hit us in 4.13, unfortunately we haven't spotted it during the 4.13 cycle. A new device id, for Gemini Lake SoC. This particular patch doesn't apply cleanly to stable kernels so I will post separated backport patches

[char-misc 2/2] mei: me: add gemini lake devices id

Add Gemini Lake (GLK) device id. Signed-off-by: Tomas Winkler --- drivers/misc/mei/hw-me-regs.h | 2 ++ drivers/misc/mei/pci-me.c | 2 ++ 2 files changed, 4 insertions(+) diff --git a/drivers/misc/mei/hw-me-regs.h b/drivers/misc/mei/hw-me-regs.h index

[char-misc 2/2] mei: me: add gemini lake devices id

Add Gemini Lake (GLK) device id. Signed-off-by: Tomas Winkler --- drivers/misc/mei/hw-me-regs.h | 2 ++ drivers/misc/mei/pci-me.c | 2 ++ 2 files changed, 4 insertions(+) diff --git a/drivers/misc/mei/hw-me-regs.h b/drivers/misc/mei/hw-me-regs.h index c8307e8b4c16..0baf530d 100644 ---

include/linux/kernel.h:860:32: error: dereferencing pointer to incomplete type 'struct clock_event_device'

Hi Ian, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: cd4175b11685b11c40e31a03e05084cc212b0649 commit: c7acec713d14c6ce8a20154f9dfda258d6bcad3b kernel.h: handle pointers to arrays better in container_of() date:

include/linux/kernel.h:860:32: error: dereferencing pointer to incomplete type 'struct clock_event_device'

Hi Ian, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: cd4175b11685b11c40e31a03e05084cc212b0649 commit: c7acec713d14c6ce8a20154f9dfda258d6bcad3b kernel.h: handle pointers to arrays better in container_of() date:

Re: [PATCH] Fix C++ kernel in include/linux/mtd/mtd.h

Am Sonntag, 24. September 2017, 10:20:06 CEST schrieb Boris Brezillon: > On Sat, 23 Sep 2017 23:10:26 +0200 > > Marek Vasut wrote: > > On 09/23/2017 10:13 PM, Pavel Machek wrote: > > > C++ comments look wrong in kernel tree. Fix one. > > > > AFAIR they are now (sadly)

Re: [PATCH] Fix C++ kernel in include/linux/mtd/mtd.h

Am Sonntag, 24. September 2017, 10:20:06 CEST schrieb Boris Brezillon: > On Sat, 23 Sep 2017 23:10:26 +0200 > > Marek Vasut wrote: > > On 09/23/2017 10:13 PM, Pavel Machek wrote: > > > C++ comments look wrong in kernel tree. Fix one. > > > > AFAIR they are now (sadly) accepted, but this patch

Re: [PATCH] Fix C++ kernel in include/linux/mtd/mtd.h

On Sat, 23 Sep 2017 23:10:26 +0200 Marek Vasut wrote: > On 09/23/2017 10:13 PM, Pavel Machek wrote: > > C++ comments look wrong in kernel tree. Fix one. > > AFAIR they are now (sadly) accepted, but this patch works for me. Works for me too. Here is my Acked-by: Boris

Re: [PATCH] Fix C++ kernel in include/linux/mtd/mtd.h

On Sat, 23 Sep 2017 23:10:26 +0200 Marek Vasut wrote: > On 09/23/2017 10:13 PM, Pavel Machek wrote: > > C++ comments look wrong in kernel tree. Fix one. > > AFAIR they are now (sadly) accepted, but this patch works for me. Works for me too. Here is my Acked-by: Boris Brezillon > Would be

[PATCH v3] block: consider merge of segments when merge bio into rq

When account the nr_phys_segments during merging bios into rq, only consider segments merging in individual bio but not all the bios in a rq. This leads to the bigger nr_phys_segments of rq than the real one when the segments of bios in rq are contiguous and mergeable. The nr_phys_segments of rq

[PATCH v3] block: consider merge of segments when merge bio into rq

When account the nr_phys_segments during merging bios into rq, only consider segments merging in individual bio but not all the bios in a rq. This leads to the bigger nr_phys_segments of rq than the real one when the segments of bios in rq are contiguous and mergeable. The nr_phys_segments of rq

Re: [PATCH V3 1/1] clk: bulk: add of_clk_bulk_get()

On Sun, Sep 24, 2017 at 4:06 AM, kbuild test robot wrote: > [auto build test ERROR on clk/clk-next] > [also build test ERROR on v4.14-rc1 next-20170922] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system] > > url: >

Re: [PATCH V3 1/1] clk: bulk: add of_clk_bulk_get()

On Sun, Sep 24, 2017 at 4:06 AM, kbuild test robot wrote: > [auto build test ERROR on clk/clk-next] > [also build test ERROR on v4.14-rc1 next-20170922] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system] > > url: >

[PATCH v6 1/2] media:imx274 device tree binding file

The binding file for imx274 CMOS sensor V4l2 driver Signed-off-by: Leon Luo --- v6: - no changes v5: - add 'port' and 'endpoint' information v4: - no changes v3: - remove redundant properties and references - document 'reg' property v2: - no changes ---

[PATCH v6 2/2] media:imx274 V4l2 driver for Sony imx274 CMOS sensor

The imx274 is a Sony CMOS image sensor that has 1/2.5 image size. It supports up to 3840x2160 (4K) 60fps, 1080p 120fps. The interface is 4-lane MIPI CSI-2 running at 1.44Gbps each. This driver has been tested on Xilinx ZCU102 platform with a Leopard LI-IMX274MIPI-FMC camera board. Support for

[PATCH v6 1/2] media:imx274 device tree binding file

The binding file for imx274 CMOS sensor V4l2 driver Signed-off-by: Leon Luo --- v6: - no changes v5: - add 'port' and 'endpoint' information v4: - no changes v3: - remove redundant properties and references - document 'reg' property v2: - no changes ---

[PATCH v6 2/2] media:imx274 V4l2 driver for Sony imx274 CMOS sensor

The imx274 is a Sony CMOS image sensor that has 1/2.5 image size. It supports up to 3840x2160 (4K) 60fps, 1080p 120fps. The interface is 4-lane MIPI CSI-2 running at 1.44Gbps each. This driver has been tested on Xilinx ZCU102 platform with a Leopard LI-IMX274MIPI-FMC camera board. Support for

Re: (*ABS*+0xbb29b267): multiple definition of `__crc___gcov_merge_add'

Am Sonntag, 24. September 2017, 08:42:06 CEST schrieb kbuild test robot: > Hi Thomas, > > FYI, the error/warning still remains. Thomas' fix will be part of the next pull request. Thanks, //richard

Re: (*ABS*+0xbb29b267): multiple definition of `__crc___gcov_merge_add'

Am Sonntag, 24. September 2017, 08:42:06 CEST schrieb kbuild test robot: > Hi Thomas, > > FYI, the error/warning still remains. Thomas' fix will be part of the next pull request. Thanks, //richard

Re: [PATCH] staging:ccree Fix avoid externs in .c files

On Thu, Sep 21, 2017 at 9:43 AM, Janani Sankara Babu wrote: > This patch solves the warning shown by the checkpatch script > WARNING: externs should be avoided in .c files I'm afraid here too the feedback is the same - you are working on the Linus master tree, therefore you

Re: [PATCH] staging:ccree Fix avoid externs in .c files

On Thu, Sep 21, 2017 at 9:43 AM, Janani Sankara Babu wrote: > This patch solves the warning shown by the checkpatch script > WARNING: externs should be avoided in .c files I'm afraid here too the feedback is the same - you are working on the Linus master tree, therefore you are seeing things

Re: [PATCH] staging:ccree Fix use BIT macro

Hi Janani, On Thu, Sep 21, 2017 at 9:39 AM, Janani Sankara Babu wrote: > This patch is created to solve the following warning shown by the checkpatch > script Warning: Replace all occurences of (1< > Signed-off-by: Janani Sankara Babu

Re: [PATCH] staging:ccree Fix use BIT macro

Hi Janani, On Thu, Sep 21, 2017 at 9:39 AM, Janani Sankara Babu wrote: > This patch is created to solve the following warning shown by the checkpatch > script Warning: Replace all occurences of (1< > Signed-off-by: Janani Sankara Babu Thank you for the patch - unfortunately, such a fix s

Re: ALSA: bebob: Use common error handling code in snd_bebob_stream_start_duplex()

> 668 if (!amdtp_stream_wait_callback(>tx_stream, > 669 CALLBACK_TIMEOUT)) { > 670 amdtp_stream_stop(>tx_stream); > 671 amdtp_stream_stop(>rx_stream); > 672 break_both_connections(bebob); > 673 err = -ETIMEDOUT; > 674 } >

Re: ALSA: bebob: Use common error handling code in snd_bebob_stream_start_duplex()

> 668 if (!amdtp_stream_wait_callback(>tx_stream, > 669 CALLBACK_TIMEOUT)) { > 670 amdtp_stream_stop(>tx_stream); > 671 amdtp_stream_stop(>rx_stream); > 672 break_both_connections(bebob); > 673 err = -ETIMEDOUT; > 674 } >

Re: [Outreachy kernel] [PATCH] drm/tegra: Replace dev_* with DRM_DEV_*

On Sun, 24 Sep 2017, Harsha Sharma wrote: > Replace all occurences of dev_info/err/dbg with DRM_DEV_INFO/ > ERROR/DEBUG as we have DRM_DEV_* variants of drm print macros > Done using following coccinelle semantic patch Some calls after under comments. They could be dropped. Some calls appear

Re: [Outreachy kernel] [PATCH] drm/tegra: Replace dev_* with DRM_DEV_*

On Sun, 24 Sep 2017, Harsha Sharma wrote: > Replace all occurences of dev_info/err/dbg with DRM_DEV_INFO/ > ERROR/DEBUG as we have DRM_DEV_* variants of drm print macros > Done using following coccinelle semantic patch Some calls after under comments. They could be dropped. Some calls appear

(*ABS*+0xbb29b267): multiple definition of `__crc___gcov_merge_add'

Hi Thomas, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: cd4175b11685b11c40e31a03e05084cc212b0649 commit: d3488649dcd23b7a6e63895274ec69f80e92d4ed um: Fix CONFIG_GCOV for modules. date: 10 days ago config:

(*ABS*+0xbb29b267): multiple definition of `__crc___gcov_merge_add'

Hi Thomas, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: cd4175b11685b11c40e31a03e05084cc212b0649 commit: d3488649dcd23b7a6e63895274ec69f80e92d4ed um: Fix CONFIG_GCOV for modules. date: 10 days ago config:

[PATCH] dmaengine: imx-sdma: Report a DMA_ERROR in status if 'count' or 'dma_address' do not match DMA_SLAVE_BUSWIDTH

All sanity checks in this function set 'sdmac->status = DMA_ERROR' if something looks wrong, except if the byte count or the address don't match the bus width. Fix it and report the error in status in such a case. Signed-off-by: Christophe JAILLET --- Untested, so

[PATCH] dmaengine: imx-sdma: Report a DMA_ERROR in status if 'count' or 'dma_address' do not match DMA_SLAVE_BUSWIDTH

All sanity checks in this function set 'sdmac->status = DMA_ERROR' if something looks wrong, except if the byte count or the address don't match the bus width. Fix it and report the error in status in such a case. Signed-off-by: Christophe JAILLET --- Untested, so please review carefuly. ---

drivers/clocksource/timer-of.h:35:28: error: field 'clkevt' has incomplete type

Hi Daniel, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: cd4175b11685b11c40e31a03e05084cc212b0649 commit: dc11bae78529526605c5c45c369c9512fd012093 clocksource/drivers: Add timer-of common init routine date: 3

drivers/clocksource/timer-of.h:35:28: error: field 'clkevt' has incomplete type

Hi Daniel, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: cd4175b11685b11c40e31a03e05084cc212b0649 commit: dc11bae78529526605c5c45c369c9512fd012093 clocksource/drivers: Add timer-of common init routine date: 3

<    8   9   10   11   12   13   14   >