[PATCH v3] ACPI / sysfs: Provide quirk mechanism to prevent GPE flooding

Sometimes, the users may require a quirk to be provided from ACPI subsystem core to prevent a GPE from flooding. Normally, if a GPE cannot be dispatched, ACPICA core automatically prevents the GPE from firing. But there are cases the GPE is dispatched by _Lxx/_Exx provided via AML table, and OSPM

[PATCH v3] ACPI / sysfs: Provide quirk mechanism to prevent GPE flooding

Sometimes, the users may require a quirk to be provided from ACPI subsystem core to prevent a GPE from flooding. Normally, if a GPE cannot be dispatched, ACPICA core automatically prevents the GPE from firing. But there are cases the GPE is dispatched by _Lxx/_Exx provided via AML table, and OSPM

Re: [PATCH RFC] user-namespaced file capabilities - now with even more magic

"Serge E. Hallyn" writes: > Root in a user ns cannot be trusted to write a traditional > security.capability xattr. If it were allowed to do so, then any > unprivileged user on the host could map his own uid to root in a > namespace, write the xattr, and execute the file with

Re: [PATCH RFC] user-namespaced file capabilities - now with even more magic

"Serge E. Hallyn" writes: > Root in a user ns cannot be trusted to write a traditional > security.capability xattr. If it were allowed to do so, then any > unprivileged user on the host could map his own uid to root in a > namespace, write the xattr, and execute the file with privilege on the >

[PATCH] x86/vm86: fix compilation warning on a unused variable

When CONFIG_TRANSPARENT_HUGEPAGE is disabled, split_huge_pmd is a no-op stub. In such case, vma is unused and a compiler raises a warning: arch/x86/kernel/vm86_32.c: In function ‘mark_screen_rdonly’: arch/x86/kernel/vm86_32.c:180:26: warning: unused variable ‘vma’ [-Wunused-variable] struct

[PATCH] x86/vm86: fix compilation warning on a unused variable

When CONFIG_TRANSPARENT_HUGEPAGE is disabled, split_huge_pmd is a no-op stub. In such case, vma is unused and a compiler raises a warning: arch/x86/kernel/vm86_32.c: In function ‘mark_screen_rdonly’: arch/x86/kernel/vm86_32.c:180:26: warning: unused variable ‘vma’ [-Wunused-variable] struct

linux-next: Tree for Dec 8

Hi all, Changes since 20161207: The powerpc allyesconfig build seems to be fixed again. The sunxi tree gained a conflict against the arm-soc tree. The tip tree lost its perf build failure. The pinctrl tree lost its build failure. I dropped 2 patches from the akpm tree that no longer apply

linux-next: Tree for Dec 8

Hi all, Changes since 20161207: The powerpc allyesconfig build seems to be fixed again. The sunxi tree gained a conflict against the arm-soc tree. The tip tree lost its perf build failure. The pinctrl tree lost its build failure. I dropped 2 patches from the akpm tree that no longer apply

[PATCH v6 2/2] crypto: add virtio-crypto driver

This patch introduces virtio-crypto driver for Linux Kernel. The virtio crypto device is a virtual cryptography device as well as a kind of virtual hardware accelerator for virtual machines. The encryption anddecryption requests are placed in the data queue and are ultimately handled by

[PATCH v6 2/2] crypto: add virtio-crypto driver

This patch introduces virtio-crypto driver for Linux Kernel. The virtio crypto device is a virtual cryptography device as well as a kind of virtual hardware accelerator for virtual machines. The encryption anddecryption requests are placed in the data queue and are ultimately handled by

[PATCH v6 1/2] sparc: fix a building error reported by kbuild

>> arch/sparc/include/asm/topology_64.h:44:44: error: implicit declaration of function 'cpu_data' [-Werror=implicit-function-declaration] #define topology_physical_package_id(cpu) (cpu_data(cpu).proc_id) ^ Let's include cpudata.h in topology_64.h.

[PATCH v6 1/2] sparc: fix a building error reported by kbuild

>> arch/sparc/include/asm/topology_64.h:44:44: error: implicit declaration of function 'cpu_data' [-Werror=implicit-function-declaration] #define topology_physical_package_id(cpu) (cpu_data(cpu).proc_id) ^ Let's include cpudata.h in topology_64.h.

Re: [PATCH v4 4/5] i2c: designware: Add slave mode as separated driver

Hi Luis, [auto build test WARNING on wsa/i2c/for-next] [also build test WARNING on next-20161207] [cannot apply to v4.9-rc8] [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/Luis-Oliveira/i2c

Re: [PATCH v4 4/5] i2c: designware: Add slave mode as separated driver

Hi Luis, [auto build test WARNING on wsa/i2c/for-next] [also build test WARNING on next-20161207] [cannot apply to v4.9-rc8] [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/Luis-Oliveira/i2c

[PATCH v6 0/2] virtio-crypto: add Linux driver

v6: - add patch 1/2 to make sparc architecture happy. [Sam] - close created sessions previousely when rekeying. - convert the priority of virtio crypto algs from 4001 to 501 which is enough. v5: - add comments for algs_lock and table_lock. [Stefan] - use kzfree instead of kfree for key

[PATCH v6 0/2] virtio-crypto: add Linux driver

v6: - add patch 1/2 to make sparc architecture happy. [Sam] - close created sessions previousely when rekeying. - convert the priority of virtio crypto algs from 4001 to 501 which is enough. v5: - add comments for algs_lock and table_lock. [Stefan] - use kzfree instead of kfree for key

Re: [PATCH 1/7] vfs - merge path_is_mountpoint() and path_is_mountpoint_rcu()

Ian Kent writes: > On Thu, 2016-12-08 at 10:30 +1300, Eric W. Biederman wrote: >> Ian Kent writes: >> >> > On Sat, 2016-12-03 at 05:13 +, Al Viro wrote: >> > > FWIW, I've folded that pile into vfs.git#work.autofs. >> > > >> > > Problems: >> > >> >

Re: [PATCH 1/7] vfs - merge path_is_mountpoint() and path_is_mountpoint_rcu()

Ian Kent writes: > On Thu, 2016-12-08 at 10:30 +1300, Eric W. Biederman wrote: >> Ian Kent writes: >> >> > On Sat, 2016-12-03 at 05:13 +, Al Viro wrote: >> > > FWIW, I've folded that pile into vfs.git#work.autofs. >> > > >> > > Problems: >> > >> > snip ... >> > >> > > * the last one

Re: linux-next: Tree for Dec 7 (kallsyms failure)

Hi all, On Wed, 7 Dec 2016 18:30:57 -0800 Randy Dunlap wrote: > > On 12/07/16 15:56, Stephen Rothwell wrote: > > > > On Wed, 7 Dec 2016 15:42:32 -0800 Randy Dunlap > > wrote: > >> > >> I started seeing this yesterday (2016-1206). > >> This is on

Re: linux-next: Tree for Dec 7 (kallsyms failure)

Hi all, On Wed, 7 Dec 2016 18:30:57 -0800 Randy Dunlap wrote: > > On 12/07/16 15:56, Stephen Rothwell wrote: > > > > On Wed, 7 Dec 2016 15:42:32 -0800 Randy Dunlap > > wrote: > >> > >> I started seeing this yesterday (2016-1206). > >> This is on x86_64. > >> > >> Anybody know about it? > >>

[PATCH 1/2] kbuild: improve EXPORT_SYMBOL() parsing from asm code

First, make the asm-prototypes.h presence optional. The next patch will make it unneeded for modversion support. Use the -D__GENKSYMS__ like we do for .c files but to expand the EXPORT_SYMBOL macro using the preprocessor instead of a sed script. The preprocessor output parsing is then limited to

[PATCH 1/2] kbuild: improve EXPORT_SYMBOL() parsing from asm code

First, make the asm-prototypes.h presence optional. The next patch will make it unneeded for modversion support. Use the -D__GENKSYMS__ like we do for .c files but to expand the EXPORT_SYMBOL macro using the preprocessor instead of a sed script. The preprocessor output parsing is then limited to

[PATCH 2/2] kbuild: make modversion for exported asm symbols more convivial

Rather than having an asm-prototypes.h file where C prototypes for exported asm symbols are centralized, let's have some macros that can be used directly in the code where those symbols are exported for genksyms consumption. Either the prototype is provided directly if no include files has it, or

[PATCH 2/2] kbuild: make modversion for exported asm symbols more convivial

Rather than having an asm-prototypes.h file where C prototypes for exported asm symbols are centralized, let's have some macros that can be used directly in the code where those symbols are exported for genksyms consumption. Either the prototype is provided directly if no include files has it, or

[PATCH 0/2] improve modversions for symbols exported from assembly code

This is a partial repost of the patches I sent last week, without the ARM part this time, in the hope that this can be considered for the next merge window so that architecture specific changes can start using it afterwards. include/asm-generic/export.h | 24

[PATCH 0/2] improve modversions for symbols exported from assembly code

This is a partial repost of the patches I sent last week, without the ARM part this time, in the hope that this can be considered for the next merge window so that architecture specific changes can start using it afterwards. include/asm-generic/export.h | 24

[PATCH v3] mach-omap2: fixing wrong strcat for Non-NULL terminated string

Issue caught with static analysis tool: "Dangerous usage of 'name' (strncpy doesn't always 0-terminate it)" Use strlcpy _includes_ the NUL terminator, and strlcat() which ensures that it won't overflow the buffer. Reported-by: Maninder Singh Signed-off-by: Vaneet

[PATCH v3] mach-omap2: fixing wrong strcat for Non-NULL terminated string

Issue caught with static analysis tool: "Dangerous usage of 'name' (strncpy doesn't always 0-terminate it)" Use strlcpy _includes_ the NUL terminator, and strlcat() which ensures that it won't overflow the buffer. Reported-by: Maninder Singh Signed-off-by: Vaneet Narang CC: Russell King ---

Re: [PATCH 2/2] mtd: spi-nor: add a stateless method to support memory size above 128Mib

On 12/07/2016 05:59 PM, Cyrille Pitchen wrote: > Le 07/12/2016 à 17:32, Marek Vasut a écrit : >> On 12/07/2016 05:29 PM, Cyrille Pitchen wrote: >>> Le 07/12/2016 à 17:20, Marek Vasut a écrit : On 12/06/2016 05:52 PM, Cyrille Pitchen wrote: > This patch provides an alternative mean to

Re: [PATCH 2/2] mtd: spi-nor: add a stateless method to support memory size above 128Mib

On 12/07/2016 05:59 PM, Cyrille Pitchen wrote: > Le 07/12/2016 à 17:32, Marek Vasut a écrit : >> On 12/07/2016 05:29 PM, Cyrille Pitchen wrote: >>> Le 07/12/2016 à 17:20, Marek Vasut a écrit : On 12/06/2016 05:52 PM, Cyrille Pitchen wrote: > This patch provides an alternative mean to

RE: [PATCH] usbip: fix warning in vhci_hcd_probe/lockdep_init_map

Dear Shuah, > I noticed that in many places sysfs_attr_init() is called before populating > the fields such as name etc. However, I don't think the order matters. > > sysfs_attr_init() doesn't depend on name or any other fields being set: > > #define sysfs_attr_init(attr)

RE: [PATCH] usbip: fix warning in vhci_hcd_probe/lockdep_init_map

Dear Shuah, > I noticed that in many places sysfs_attr_init() is called before populating > the fields such as name etc. However, I don't think the order matters. > > sysfs_attr_init() doesn't depend on name or any other fields being set: > > #define sysfs_attr_init(attr)

linux-next: patches dropped from the akpm tree

Hi Andrew, While rebasing the post -next part of your tree today, I dropped these patches: drivers/clk/uniphier/clk-uniphier.h: fix build with old gcc drivers/clk/uniphier/clk-uniphier-mio.c: fix build for older gcc Some commits in other trees that modified these files have been dropped and

linux-next: patches dropped from the akpm tree

Hi Andrew, While rebasing the post -next part of your tree today, I dropped these patches: drivers/clk/uniphier/clk-uniphier.h: fix build with old gcc drivers/clk/uniphier/clk-uniphier-mio.c: fix build for older gcc Some commits in other trees that modified these files have been dropped and

Re: [PATCH 07/12] PM / OPP: Update OPP users to put reference

On 07-12-16, 22:23, Chanwoo Choi wrote: > I think that the dev_pm_opp_put(opp) should be called after if statement > If dev_pm_opp_find_freq_ceil() return error, I think the calling of > dev_pm_opp_put(opp) is not necessary. During development I had following check in dev_pm_opp_put():

Re: [PATCH 07/12] PM / OPP: Update OPP users to put reference

On 07-12-16, 22:23, Chanwoo Choi wrote: > I think that the dev_pm_opp_put(opp) should be called after if statement > If dev_pm_opp_find_freq_ceil() return error, I think the calling of > dev_pm_opp_put(opp) is not necessary. During development I had following check in dev_pm_opp_put():

[PATCH 2/2] arm64:dt:ls1012a: Add TMU device tree support for LS1012A

Also add nodes and properties for thermal management support. Signed-off-by: Jia Hongtao --- Depend on patch "[v3] arm64: Add DTS support for FSL's LS1012A SoC". https://patchwork.kernel.org/patch/9462399/ arch/arm64/boot/dts/freescale/fsl-ls1012a.dtsi | 76

[PATCH 2/2] arm64:dt:ls1012a: Add TMU device tree support for LS1012A

Also add nodes and properties for thermal management support. Signed-off-by: Jia Hongtao --- Depend on patch "[v3] arm64: Add DTS support for FSL's LS1012A SoC". https://patchwork.kernel.org/patch/9462399/ arch/arm64/boot/dts/freescale/fsl-ls1012a.dtsi | 76 ++ 1 file

Re: [RFC 06/10] block: use tida as small id allocator

On 12/07/2016 06:23 PM, Rasmus Villemoes wrote: > A struct ida ends up costing > 16 KB of runtime memory, which is quite > a lot for something which on my laptop as of this writing has handed > out 27 ids in its lifetime. So use the simpler and lighter-weight > struct tida. I'm worried that your

Re: [RFC 06/10] block: use tida as small id allocator

On 12/07/2016 06:23 PM, Rasmus Villemoes wrote: > A struct ida ends up costing > 16 KB of runtime memory, which is quite > a lot for something which on my laptop as of this writing has handed > out 27 ids in its lifetime. So use the simpler and lighter-weight > struct tida. I'm worried that your

Re: [PATCH] powerpc: Fix LPCR_VRMASD definition

Jia He writes: > Fixes: a4b349540a ("powerpc/mm: Cleanup LPCR defines") > Signed-off-by: Jia He I sent another one https://lkml.kernel.org/r/20161208034213.21700-1-aneesh.ku...@linux.vnet.ibm.com to fix the same issue. I didn't notice this on the list.

Re: [PATCH] powerpc: Fix LPCR_VRMASD definition

Jia He writes: > Fixes: a4b349540a ("powerpc/mm: Cleanup LPCR defines") > Signed-off-by: Jia He I sent another one https://lkml.kernel.org/r/20161208034213.21700-1-aneesh.ku...@linux.vnet.ibm.com to fix the same issue. I didn't notice this on the list. > --- >

Re: [PATCH 1/7] vfs - merge path_is_mountpoint() and path_is_mountpoint_rcu()

On Thu, 2016-12-08 at 10:30 +1300, Eric W. Biederman wrote: > Ian Kent writes: > > > On Sat, 2016-12-03 at 05:13 +, Al Viro wrote: > > > FWIW, I've folded that pile into vfs.git#work.autofs. > > > > > > Problems: > > > > snip ... > > > > > * the last one

Re: [PATCH 1/7] vfs - merge path_is_mountpoint() and path_is_mountpoint_rcu()

On Thu, 2016-12-08 at 10:30 +1300, Eric W. Biederman wrote: > Ian Kent writes: > > > On Sat, 2016-12-03 at 05:13 +, Al Viro wrote: > > > FWIW, I've folded that pile into vfs.git#work.autofs. > > > > > > Problems: > > > > snip ... > > > > > * the last one (propagation-related) is too

[PATCH] powerpc: Fix LPCR_VRMASD definition

Fixes: a4b349540a ("powerpc/mm: Cleanup LPCR defines") Signed-off-by: Jia He --- arch/powerpc/include/asm/reg.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/powerpc/include/asm/reg.h b/arch/powerpc/include/asm/reg.h index 9e1499f..93ec25e 100644

[PATCH] powerpc: Fix LPCR_VRMASD definition

Fixes: a4b349540a ("powerpc/mm: Cleanup LPCR defines") Signed-off-by: Jia He --- arch/powerpc/include/asm/reg.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/powerpc/include/asm/reg.h b/arch/powerpc/include/asm/reg.h index 9e1499f..93ec25e 100644 ---

Re: [PATCH v2] kexec: add cond_resched into kimage_alloc_crash_control_pages

zhongjiang writes: > From: zhong jiang > > A soft lookup will occur when I run trinity in syscall kexec_load. > the corresponding stack information is as follows. Acked-by: "Eric W. Biederman" > > [ 237.235937] BUG: soft

Re: [PATCH v2] kexec: add cond_resched into kimage_alloc_crash_control_pages

zhongjiang writes: > From: zhong jiang > > A soft lookup will occur when I run trinity in syscall kexec_load. > the corresponding stack information is as follows. Acked-by: "Eric W. Biederman" > > [ 237.235937] BUG: soft lockup - CPU#6 stuck for 22s! [trinity-c6:13859] > [ 237.242699]

Re: [Linaro-acpi] [PATCH v17 08/15] clocksource/drivers/arm_arch_timer: move arch_timer_needs_of_probing into DT init call

Hi Timur, On 8 December 2016 at 01:25, Timur Tabi wrote: > On Fri, Nov 25, 2016 at 9:06 AM, Fu Wei wrote: >> >> a "+ int ret;" should be move from [12/15] to here, I have fix the >> problem in my repo, it would happen in next patchset >> >>

Re: [Linaro-acpi] [PATCH v17 08/15] clocksource/drivers/arm_arch_timer: move arch_timer_needs_of_probing into DT init call

Hi Timur, On 8 December 2016 at 01:25, Timur Tabi wrote: > On Fri, Nov 25, 2016 at 9:06 AM, Fu Wei wrote: >> >> a "+ int ret;" should be move from [12/15] to here, I have fix the >> problem in my repo, it would happen in next patchset >> >>

Re: [PATCH 1/2] usb: dwc3: gadget: Fix full speed mode

On 12/7/2016 4:44 AM, Felipe Balbi wrote: > > Hi, > > Roger Quadros writes: Roger Quadros writes: > DCFG.DEVSPD == 0x3 is not valid and we need to set > DCFG.DEVSPD to 0x1 for full speed mode. seems like it has been made invalid somewhere

Re: [PATCH 1/2] usb: dwc3: gadget: Fix full speed mode

On 12/7/2016 4:44 AM, Felipe Balbi wrote: > > Hi, > > Roger Quadros writes: Roger Quadros writes: > DCFG.DEVSPD == 0x3 is not valid and we need to set > DCFG.DEVSPD to 0x1 for full speed mode. seems like it has been made invalid somewhere between 1.73a and 2.60a.

[PATCH] f2fs: fix to access nullified flush_cmd_control pointer

f2fs_sync_file() remount_ro - f2fs_readonly - destroy_flush_cmd_control - f2fs_issue_flush - no fcc pointer! So, this patch doesn't free fcc in this case, but just stop its kernel thread which sends flush commands. Signed-off-by: Jaegeuk Kim

[PATCH] f2fs: fix to access nullified flush_cmd_control pointer

f2fs_sync_file() remount_ro - f2fs_readonly - destroy_flush_cmd_control - f2fs_issue_flush - no fcc pointer! So, this patch doesn't free fcc in this case, but just stop its kernel thread which sends flush commands. Signed-off-by: Jaegeuk Kim ---

Re: [PATCH] ARM: multi_v7_defconfig: set bcm47xx watchdog

Le 12/02/16 à 01:42, Valentin Rothberg a écrit : > Correct the bcm47xx watchdog option. The convention of bcm watchdogs is > the _WDT suffix. > > Signed-off-by: Valentin Rothberg Also applied; thanks! -- Florian

Re: [PATCH] ARM: multi_v7_defconfig: set bcm47xx watchdog

Le 12/02/16 à 01:42, Valentin Rothberg a écrit : > Correct the bcm47xx watchdog option. The convention of bcm watchdogs is > the _WDT suffix. > > Signed-off-by: Valentin Rothberg Also applied; thanks! -- Florian

Re: [PATCH] ARM: multi_v7_defconfig: fix config typo

Le 12/02/16 à 01:24, Valentin Rothberg a écrit : > s/CONFIG_CONFIG_BCM47XX_NVRAM/CONFIG_BCM47XX_NVRAM/ > > Signed-off-by: Valentin Rothberg Applied thanks! -- Florian

Re: [PATCH] ARM: multi_v7_defconfig: fix config typo

Le 12/02/16 à 01:24, Valentin Rothberg a écrit : > s/CONFIG_CONFIG_BCM47XX_NVRAM/CONFIG_BCM47XX_NVRAM/ > > Signed-off-by: Valentin Rothberg Applied thanks! -- Florian

Re: [PATCH] usbip: fix warning in vhci_hcd_probe/lockdep_init_map

Hi Nobuo.iwata, I noticed that in many places sysfs_attr_init() is called before populating the fields such as name etc. However, I don't think the order matters. sysfs_attr_init() doesn't depend on name or any other fields being set: #define sysfs_attr_init(attr) \ do

Re: [PATCH] usbip: fix warning in vhci_hcd_probe/lockdep_init_map

Hi Nobuo.iwata, I noticed that in many places sysfs_attr_init() is called before populating the fields such as name etc. However, I don't think the order matters. sysfs_attr_init() doesn't depend on name or any other fields being set: #define sysfs_attr_init(attr) \ do

Re: [PATCH 01/11] mm, devm_memremap_pages: use multi-order radix for ZONE_DEVICE lookups

On Thu, Dec 1, 2016 at 2:29 PM, Dan Williams wrote: > devm_memremap_pages() records mapped ranges in pgmap_radix with a entry > per section's worth of memory (128MB). The key for each of those entries is > a section number. > > This leads to false positives when

Re: [PATCH 01/11] mm, devm_memremap_pages: use multi-order radix for ZONE_DEVICE lookups

On Thu, Dec 1, 2016 at 2:29 PM, Dan Williams wrote: > devm_memremap_pages() records mapped ranges in pgmap_radix with a entry > per section's worth of memory (128MB). The key for each of those entries is > a section number. > > This leads to false positives when devm_memremap_pages() is passed a

[PATCH v2] kexec: add cond_resched into kimage_alloc_crash_control_pages

From: zhong jiang A soft lookup will occur when I run trinity in syscall kexec_load. the corresponding stack information is as follows. [ 237.235937] BUG: soft lockup - CPU#6 stuck for 22s! [trinity-c6:13859] [ 237.242699] Kernel panic - not syncing: softlockup: hung

[PATCH v2] kexec: add cond_resched into kimage_alloc_crash_control_pages

From: zhong jiang A soft lookup will occur when I run trinity in syscall kexec_load. the corresponding stack information is as follows. [ 237.235937] BUG: soft lockup - CPU#6 stuck for 22s! [trinity-c6:13859] [ 237.242699] Kernel panic - not syncing: softlockup: hung tasks [ 237.248573] CPU:

Re: [PATCH] drm/mxsfb: fix pixel clock polarity

On 12/08/2016 02:26 AM, Stefan Agner wrote: > On 2016-12-07 16:59, Stefan Agner wrote: >> On 2016-12-07 16:49, Marek Vasut wrote: >>> On 12/08/2016 01:27 AM, Stefan Agner wrote: The DRM subsystem specifies the pixel clock polarity from a controllers perspective:

Re: [PATCH] drm/mxsfb: fix pixel clock polarity

On 12/08/2016 02:26 AM, Stefan Agner wrote: > On 2016-12-07 16:59, Stefan Agner wrote: >> On 2016-12-07 16:49, Marek Vasut wrote: >>> On 12/08/2016 01:27 AM, Stefan Agner wrote: The DRM subsystem specifies the pixel clock polarity from a controllers perspective:

Re: linux-next: Tree for Dec 7 (kallsyms failure)

On 12/07/16 15:56, Stephen Rothwell wrote: > Hi Randy, > > On Wed, 7 Dec 2016 15:42:32 -0800 Randy Dunlap wrote: >> >> I started seeing this yesterday (2016-1206). >> This is on x86_64. >> >> Anybody know about it? >> >> kallsyms failure: relative symbol value

Re: linux-next: Tree for Dec 7 (kallsyms failure)

On 12/07/16 15:56, Stephen Rothwell wrote: > Hi Randy, > > On Wed, 7 Dec 2016 15:42:32 -0800 Randy Dunlap wrote: >> >> I started seeing this yesterday (2016-1206). >> This is on x86_64. >> >> Anybody know about it? >> >> kallsyms failure: relative symbol value 0x8100 out of range in

[PATCH] linux/types.h: enable endian checks for all sparse builds

By now, linux is mostly endian-clean. Enabling endian-ness checks for everyone produces about 200 new sparse warnings for me - less than 10% over the 2000 sparse warnings already there. Not a big deal, OTOH enabling this helps people notice they are introducing new bugs. So let's just drop

[PATCH] linux/types.h: enable endian checks for all sparse builds

By now, linux is mostly endian-clean. Enabling endian-ness checks for everyone produces about 200 new sparse warnings for me - less than 10% over the 2000 sparse warnings already there. Not a big deal, OTOH enabling this helps people notice they are introducing new bugs. So let's just drop

RE: [PATCH] usbip: fix warning in vhci_hcd_probe/lockdep_init_map

Dear Shuah, I'm afraid there's one thing I have concerned. I think it's better to move sysfs_attr_init() before status->attr.attr.name = status->name; Best Regards, nobuo.iwata // > -Original Message- > From: linux-usb-ow...@vger.kernel.org > [mailto:linux-usb-ow...@vger.kernel.org] On

RE: [PATCH] usbip: fix warning in vhci_hcd_probe/lockdep_init_map

Dear Shuah, I'm afraid there's one thing I have concerned. I think it's better to move sysfs_attr_init() before status->attr.attr.name = status->name; Best Regards, nobuo.iwata // > -Original Message- > From: linux-usb-ow...@vger.kernel.org > [mailto:linux-usb-ow...@vger.kernel.org] On

Re: [PATCH] MAINTAINERS: Add Patchwork URL to Samsung Exynos entry

2016. 12. 8. 02:18 Krzysztof Kozlowski wrote: > I use Patchwork for handling incoming patches. Put its address here so > submitters could know what is in the queue. > Signed-off-by: Krzysztof Kozlowski > --- > MAINTAINERS | 1 + > 1 file changed, 1 insertion(+)

Re: [PATCH] MAINTAINERS: Add Patchwork URL to Samsung Exynos entry

2016. 12. 8. 02:18 Krzysztof Kozlowski wrote: > I use Patchwork for handling incoming patches. Put its address here so > submitters could know what is in the queue. > Signed-off-by: Krzysztof Kozlowski > --- > MAINTAINERS | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/MAINTAINERS

Re: [PATCH] kexec: add cond_resched into kimage_alloc_crash_control_pages

On 2016/12/8 9:50, Eric W. Biederman wrote: > zhongjiang writes: > >> From: zhong jiang >> >> A soft lookup will occur when I run trinity in syscall kexec_load. >> the corresponding stack information is as follows. > Overall that looks reasonable.

Re: [PATCH] kexec: add cond_resched into kimage_alloc_crash_control_pages

On 2016/12/8 9:50, Eric W. Biederman wrote: > zhongjiang writes: > >> From: zhong jiang >> >> A soft lookup will occur when I run trinity in syscall kexec_load. >> the corresponding stack information is as follows. > Overall that looks reasonable. Why only every 256 page and not call >

Re: [PATCH v3 4/4] pinctrl: aspeed: Fix kerneldoc return descriptions

On Tue, Dec 6, 2016 at 1:41 PM, Andrew Jeffery wrote: > Signed-off-by: Andrew Jeffery Acked-by: Joel Stanley > --- > drivers/pinctrl/aspeed/pinctrl-aspeed.c | 12 ++-- > 1 file changed, 6 insertions(+), 6 deletions(-)

Re: [PATCH v3 4/4] pinctrl: aspeed: Fix kerneldoc return descriptions

On Tue, Dec 6, 2016 at 1:41 PM, Andrew Jeffery wrote: > Signed-off-by: Andrew Jeffery Acked-by: Joel Stanley > --- > drivers/pinctrl/aspeed/pinctrl-aspeed.c | 12 ++-- > 1 file changed, 6 insertions(+), 6 deletions(-)

Re: [PATCH v3 1/4] pinctrl: aspeed: Read and write bits in LPC and GFX controllers

On Tue, Dec 6, 2016 at 1:41 PM, Andrew Jeffery wrote: > The System Control Unit IP block in the Aspeed SoCs is typically where > the pinmux configuration is found, but not always. A number of pins > depend on state in one of LPC Host Control (LHC) or SoC Display > Controller

Re: [PATCH v3 1/4] pinctrl: aspeed: Read and write bits in LPC and GFX controllers

On Tue, Dec 6, 2016 at 1:41 PM, Andrew Jeffery wrote: > The System Control Unit IP block in the Aspeed SoCs is typically where > the pinmux configuration is found, but not always. A number of pins > depend on state in one of LPC Host Control (LHC) or SoC Display > Controller (GFX) IP blocks, so

[PATCH] kcov: add more missing include

It is fragile that some definitions acquired via transitive dependencies, as shown in below: atomic_*() ENOMEM/EN* () EXPORT_SYMBOL () device_initcall () preempt_* () Include them to prevent possible issues. Suggested-by: Mark Rutland Signed-off-by:

[PATCH] kcov: add more missing include

It is fragile that some definitions acquired via transitive dependencies, as shown in below: atomic_*() ENOMEM/EN* () EXPORT_SYMBOL () device_initcall () preempt_* () Include them to prevent possible issues. Suggested-by: Mark Rutland Signed-off-by: Kefeng Wang ---

Re: [PATCH v3 1/3] soc: zte: pm_domains: Prepare for supporting ARMv8 2967 family

2016-12-07 14:13 GMT+08:00 Baoyou Xie : > The ARMv8 2967 family (296718, 296716 etc) uses different value > for controlling the power domain on/off registers, Choose the > value depending on the compatible. > > Multiple domains are prepared for the family, this patch

Re: [PATCH v3 1/3] soc: zte: pm_domains: Prepare for supporting ARMv8 2967 family

2016-12-07 14:13 GMT+08:00 Baoyou Xie : > The ARMv8 2967 family (296718, 296716 etc) uses different value > for controlling the power domain on/off registers, Choose the > value depending on the compatible. > > Multiple domains are prepared for the family, this patch prepares > the common

Re: [PATCH v8] Input: synaptics-rmi4 - add support for F34 V7 bootloader

Hi Nick, On Mon, Dec 05, 2016 at 01:02:49AM +, Nick Dyer wrote: > +static void rmi_f34v7_parse_img_header_10_bl_container(struct f34_data *f34, > +const u8 *image) > +{ > + int i; > + u8 num_of_containers; > + unsigned int addr;

Re: [PATCH v8] Input: synaptics-rmi4 - add support for F34 V7 bootloader

Hi Nick, On Mon, Dec 05, 2016 at 01:02:49AM +, Nick Dyer wrote: > +static void rmi_f34v7_parse_img_header_10_bl_container(struct f34_data *f34, > +const u8 *image) > +{ > + int i; > + u8 num_of_containers; > + unsigned int addr;

Re: [PATCH v3 4/6] mfd: dt: Add bindings for the Aspeed LPC Host Controller (LHC)

On Tue, Dec 6, 2016 at 1:23 PM, Andrew Jeffery wrote: > The LPC bus pinmux configuration on fifth generation Aspeed SoCs depends > on bits in both the System Control Unit and the LPC Host Controller. > > The Aspeed LPC Host Controller is described as a child node of the > LPC

Re: [PATCH v3 4/6] mfd: dt: Add bindings for the Aspeed LPC Host Controller (LHC)

On Tue, Dec 6, 2016 at 1:23 PM, Andrew Jeffery wrote: > The LPC bus pinmux configuration on fifth generation Aspeed SoCs depends > on bits in both the System Control Unit and the LPC Host Controller. > > The Aspeed LPC Host Controller is described as a child node of the > LPC host-range syscon

RE: [PATCH v5 1/1] crypto: add virtio-crypto driver

Hi Sam, > > Subject: Re: [PATCH v5 1/1] crypto: add virtio-crypto driver > > On Mon, Dec 05, 2016 at 03:12:52AM +, Gonglei (Arei) wrote: > > I don't think the root cause of those warnings are introduced by > > virtio-crypto > driver. > > > > What's your opinion? Sam and David? > > Root

RE: [PATCH v5 1/1] crypto: add virtio-crypto driver

Hi Sam, > > Subject: Re: [PATCH v5 1/1] crypto: add virtio-crypto driver > > On Mon, Dec 05, 2016 at 03:12:52AM +, Gonglei (Arei) wrote: > > I don't think the root cause of those warnings are introduced by > > virtio-crypto > driver. > > > > What's your opinion? Sam and David? > > Root

Re: [PATCH v3 3/6] mfd: dt: Add Aspeed Low Pin Count Controller bindings

On Tue, Dec 6, 2016 at 1:23 PM, Andrew Jeffery wrote: > Signed-off-by: Andrew Jeffery Reviewed-by: Joel Stanley > --- > .../devicetree/bindings/mfd/aspeed-lpc.txt | 111 > + > 1 file changed, 111 insertions(+) >

Re: [PATCH v3 3/6] mfd: dt: Add Aspeed Low Pin Count Controller bindings

On Tue, Dec 6, 2016 at 1:23 PM, Andrew Jeffery wrote: > Signed-off-by: Andrew Jeffery Reviewed-by: Joel Stanley > --- > .../devicetree/bindings/mfd/aspeed-lpc.txt | 111 > + > 1 file changed, 111 insertions(+) > create mode 100644

Re: [PATCH] mfd: axp20x: correct a typo in axp20x_device_remove documentation

On Mon, Dec 5, 2016 at 8:15 PM, Corentin Labbe wrote: > The documentation of axp20x_device_remove() have a typo and use > axp20x_device_probe() as name. > This patch fix this typo. > > Signed-off-by: Corentin Labbe Acked-by: Chen-Yu Tsai

Re: [PATCH] mfd: axp20x: correct a typo in axp20x_device_remove documentation

On Mon, Dec 5, 2016 at 8:15 PM, Corentin Labbe wrote: > The documentation of axp20x_device_remove() have a typo and use > axp20x_device_probe() as name. > This patch fix this typo. > > Signed-off-by: Corentin Labbe Acked-by: Chen-Yu Tsai

RE: [PATCH v5 1/1] crypto: add virtio-crypto driver

> > Subject: Re: [PATCH v5 1/1] crypto: add virtio-crypto driver > > On Tue, Dec 06, 2016 at 09:01:49AM +, Gonglei (Arei) wrote: > > > > Would you please review and/or ack the virtio_crypto_algs.c? > > It is the realization of specified algs based on Linux Crypto Framework. > > I have no

RE: [PATCH v5 1/1] crypto: add virtio-crypto driver

> > Subject: Re: [PATCH v5 1/1] crypto: add virtio-crypto driver > > On Tue, Dec 06, 2016 at 09:01:49AM +, Gonglei (Arei) wrote: > > > > Would you please review and/or ack the virtio_crypto_algs.c? > > It is the realization of specified algs based on Linux Crypto Framework. > > I have no

Re: [PATCH v5 01/14] Documentation: of: add type property

Hi Rob > > From: Kuninori Morimoto > > > > OF graph indicates each devices connection. But it doesn't support type > > of each port. For example HDMI case, it has video port and sound port > > in one device node. > > In this case, current driver can't handle

Re: [PATCH v5 01/14] Documentation: of: add type property

Hi Rob > > From: Kuninori Morimoto > > > > OF graph indicates each devices connection. But it doesn't support type > > of each port. For example HDMI case, it has video port and sound port > > in one device node. > > In this case, current driver can't handle each port correctly. > > This patch

Re: [PATCH] kexec: add cond_resched into kimage_alloc_crash_control_pages

zhongjiang writes: > From: zhong jiang > > A soft lookup will occur when I run trinity in syscall kexec_load. > the corresponding stack information is as follows. Overall that looks reasonable. Why only every 256 page and not call cond_resched

Re: [PATCH] kexec: add cond_resched into kimage_alloc_crash_control_pages

zhongjiang writes: > From: zhong jiang > > A soft lookup will occur when I run trinity in syscall kexec_load. > the corresponding stack information is as follows. Overall that looks reasonable. Why only every 256 page and not call cond_resched unconditionally? The function cond_resched won't

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