Applied "media: i2c: tda1997: replace codec to component" to the asoc tree

The patch media: i2c: tda1997: replace codec to component has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent

Applied "media: i2c: tda1997: replace codec to component" to the asoc tree

The patch media: i2c: tda1997: replace codec to component has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent

[PATCH v2] phy: phy-mtk-tphy: use SPDX license tag

Use SPDX-License-Identifier tag instead of the GPL license text Signed-off-by: Chunfeng Yun --- v2: change subject line to fix checkpatch warning: "A patch subject line should describe the change not the tool that found it" --- drivers/phy/mediatek/Makefile

[PATCH v2] phy: phy-mtk-tphy: use SPDX license tag

Use SPDX-License-Identifier tag instead of the GPL license text Signed-off-by: Chunfeng Yun --- v2: change subject line to fix checkpatch warning: "A patch subject line should describe the change not the tool that found it" --- drivers/phy/mediatek/Makefile | 1 +

Applied "regulator: add dummy function of_find_regulator_by_node" to the regulator tree

The patch regulator: add dummy function of_find_regulator_by_node has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next

Applied "regulator: add dummy function of_find_regulator_by_node" to the regulator tree

The patch regulator: add dummy function of_find_regulator_by_node has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next

Applied "regulator: pfuze100: Make the node name generic" to the regulator tree

The patch regulator: pfuze100: Make the node name generic has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours)

Applied "regulator: pfuze100: Make the node name generic" to the regulator tree

The patch regulator: pfuze100: Make the node name generic has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours)

[PATCH] i2c: core-smbus: fix a potential uninitialization bug

In i2c_smbus_xfer_emulated(), there are two buffers: msgbuf0 and msgbuf1, which are used to save a series of messages, as mentioned in the comment. According to the value of the variable "size", msgbuf0 is initialized to various values. In contrast, msgbuf1 is left uninitialized until the function

[PATCH] i2c: core-smbus: fix a potential uninitialization bug

In i2c_smbus_xfer_emulated(), there are two buffers: msgbuf0 and msgbuf1, which are used to save a series of messages, as mentioned in the comment. According to the value of the variable "size", msgbuf0 is initialized to various values. In contrast, msgbuf1 is left uninitialized until the function

Re: [PATCH] MAINTAINERS: Update Kbuild entry with a few paths

2018-03-23 5:58 GMT+09:00 Rasmus Villemoes : > I managed to send some modpost patches to old addresses of both > Masahiro and Michal, and omitted linux-kbuild from cc, because my > tried and trusted scripts/get_maintainer wrapper failed me. Add the > modpost directory to

Re: [PATCH] MAINTAINERS: Update Kbuild entry with a few paths

2018-03-23 5:58 GMT+09:00 Rasmus Villemoes : > I managed to send some modpost patches to old addresses of both > Masahiro and Michal, and omitted linux-kbuild from cc, because my > tried and trusted scripts/get_maintainer wrapper failed me. Add the > modpost directory to the MAINTAINERS entry, and

Re: [PATCH v2 net-next 1/4] umh: introduce fork_usermode_blob() helper

On Fri, May 04, 2018 at 07:56:43PM +, Luis R. Rodriguez wrote: > What a mighty short list of reviewers. Adding some more. My review below. > I'd appreciate a Cc on future versions of these patches. sure. > On Wed, May 02, 2018 at 09:36:01PM -0700, Alexei Starovoitov wrote: > > Introduce

Re: [PATCH v2 net-next 1/4] umh: introduce fork_usermode_blob() helper

On Fri, May 04, 2018 at 07:56:43PM +, Luis R. Rodriguez wrote: > What a mighty short list of reviewers. Adding some more. My review below. > I'd appreciate a Cc on future versions of these patches. sure. > On Wed, May 02, 2018 at 09:36:01PM -0700, Alexei Starovoitov wrote: > > Introduce

Re: [PATCH 01/30] gcc-plugins: fix build condition of SANCOV plugin

2018-05-05 1:21 GMT+09:00 Kees Cook : > On Fri, May 4, 2018 at 7:21 AM, Masahiro Yamada > wrote: >> Hi Kees, >> >> >> 2018-04-13 14:06 GMT+09:00 Masahiro Yamada : >>> Since commit d677a4d60193 ("Makefile: support

Re: [PATCH 01/30] gcc-plugins: fix build condition of SANCOV plugin

2018-05-05 1:21 GMT+09:00 Kees Cook : > On Fri, May 4, 2018 at 7:21 AM, Masahiro Yamada > wrote: >> Hi Kees, >> >> >> 2018-04-13 14:06 GMT+09:00 Masahiro Yamada : >>> Since commit d677a4d60193 ("Makefile: support flag >>> -fsanitizer-coverage=trace-cmp"), you miss to build the SANCOV >>> plugin

Re: [PATCH] i2c: core-smbus: fix a potential uninitialization bug

On Fri, May 4, 2018 at 10:38 AM, Peter Rosin wrote: > On 2018-05-04 16:59, Wenwen Wang wrote: >> On Fri, May 4, 2018 at 2:27 AM, Peter Rosin wrote: >>> On 2018-05-04 09:17, Wenwen Wang wrote: On Fri, May 4, 2018 at 1:49 AM, Peter Rosin

Re: [PATCH] i2c: core-smbus: fix a potential uninitialization bug

On Fri, May 4, 2018 at 10:38 AM, Peter Rosin wrote: > On 2018-05-04 16:59, Wenwen Wang wrote: >> On Fri, May 4, 2018 at 2:27 AM, Peter Rosin wrote: >>> On 2018-05-04 09:17, Wenwen Wang wrote: On Fri, May 4, 2018 at 1:49 AM, Peter Rosin wrote: > On 2018-05-04 07:28, Wenwen Wang wrote:

Re: [RFC PATCH] driver core: make deferring probe forever optional

On Wed, May 02, 2018 at 07:49:57PM +0100, Robin Murphy wrote: > I guess there's also the possibility that a single driver may want multiple > behaviours, if e.g. if SoC variants A and B have some identical peripherals > but slightly different pinctrl/IOMMU/etc. hardware such that A has workable >

Re: [RFC PATCH] driver core: make deferring probe forever optional

On Wed, May 02, 2018 at 07:49:57PM +0100, Robin Murphy wrote: > I guess there's also the possibility that a single driver may want multiple > behaviours, if e.g. if SoC variants A and B have some identical peripherals > but slightly different pinctrl/IOMMU/etc. hardware such that A has workable >

[PATCH 24/24] selftests: net: return Kselftest Skip code for skipped tests

When net test is skipped because of unmet dependencies and/or unsupported configuration, it returns 0 which is treated as a pass by the Kselftest framework. This leads to false positive result even when the test could not be run. Change it to return kselftest skip code when a test gets skipped to

[PATCH 23/24] selftests: mqueue: return Kselftest Skip code for skipped tests

When mqueue test is skipped because of unmet dependencies and/or unsupported configuration, it exits with error which is treated as a fail by the Kselftest framework. This leads to false negative result even when the test could not be run. Change it to return kselftest skip code when a test gets

[PATCH 24/24] selftests: net: return Kselftest Skip code for skipped tests

When net test is skipped because of unmet dependencies and/or unsupported configuration, it returns 0 which is treated as a pass by the Kselftest framework. This leads to false positive result even when the test could not be run. Change it to return kselftest skip code when a test gets skipped to

[PATCH 23/24] selftests: mqueue: return Kselftest Skip code for skipped tests

When mqueue test is skipped because of unmet dependencies and/or unsupported configuration, it exits with error which is treated as a fail by the Kselftest framework. This leads to false negative result even when the test could not be run. Change it to return kselftest skip code when a test gets

[PATCH 21/24] selftests: memfd: return Kselftest Skip code for skipped tests

When memfd test is skipped because of unmet dependencies and/or unsupported configuration, it returns non-zero value which is treated as a fail by the Kselftest framework. This leads to false negative result even when the test could not be run. Change it to return kselftest skip code when a test

[PATCH 21/24] selftests: memfd: return Kselftest Skip code for skipped tests

When memfd test is skipped because of unmet dependencies and/or unsupported configuration, it returns non-zero value which is treated as a fail by the Kselftest framework. This leads to false negative result even when the test could not be run. Change it to return kselftest skip code when a test

[PATCH 22/24] selftests: memory-hotplug: return Kselftest Skip code for skipped tests

When memory-hotplug test is skipped because of unmet dependencies and/or unsupported configuration, it returns non-zero value hich is treated as a fail by the Kselftest framework. This leads to false negative result even when the test could not be run. Change it to return kselftest skip code when

[PATCH 22/24] selftests: memory-hotplug: return Kselftest Skip code for skipped tests

When memory-hotplug test is skipped because of unmet dependencies and/or unsupported configuration, it returns non-zero value hich is treated as a fail by the Kselftest framework. This leads to false negative result even when the test could not be run. Change it to return kselftest skip code when

[PATCH 20/24] selftests: membarrier: return Kselftest Skip code for skipped tests

When membarrier test is skipped because of unmet dependencies and/or unsupported configuration, it exits with error which is treated as a fail by the Kselftest framework. This leads to false negative result even when the test could not be run. Change it to return kselftest skip code when a test

[PATCH 19/24] selftests: media_tests: return Kselftest Skip code for skipped tests

When media_tests test is skipped because of unmet dependencies and/or unsupported configuration, it exits with error which is treated as a fail by the Kselftest framework. This leads to false negative result even when the test could not be run. Change it to return kselftest skip code when a test

[PATCH 17/24] selftests: locking: add Makefile for locking test

Add Makefile for locking test. Signed-off-by: Shuah Khan (Samsung OSG) --- tools/testing/selftests/locking/Makefile | 10 ++ 1 file changed, 10 insertions(+) create mode 100644 tools/testing/selftests/locking/Makefile diff --git

[PATCH 20/24] selftests: membarrier: return Kselftest Skip code for skipped tests

When membarrier test is skipped because of unmet dependencies and/or unsupported configuration, it exits with error which is treated as a fail by the Kselftest framework. This leads to false negative result even when the test could not be run. Change it to return kselftest skip code when a test

[PATCH 19/24] selftests: media_tests: return Kselftest Skip code for skipped tests

When media_tests test is skipped because of unmet dependencies and/or unsupported configuration, it exits with error which is treated as a fail by the Kselftest framework. This leads to false negative result even when the test could not be run. Change it to return kselftest skip code when a test

[PATCH 17/24] selftests: locking: add Makefile for locking test

Add Makefile for locking test. Signed-off-by: Shuah Khan (Samsung OSG) --- tools/testing/selftests/locking/Makefile | 10 ++ 1 file changed, 10 insertions(+) create mode 100644 tools/testing/selftests/locking/Makefile diff --git a/tools/testing/selftests/locking/Makefile

[PATCH 18/24] selftests: locking: return Kselftest Skip code for skipped tests

When locking test is skipped because of unmet dependencies and/or unsupported configuration, it exits with error which is treated as a fail by the Kselftest framework. This leads to false negative result even when the test could not be run. Change it to return kselftest skip code when a test gets

[PATCH 18/24] selftests: locking: return Kselftest Skip code for skipped tests

When locking test is skipped because of unmet dependencies and/or unsupported configuration, it exits with error which is treated as a fail by the Kselftest framework. This leads to false negative result even when the test could not be run. Change it to return kselftest skip code when a test gets

[PATCH 16/24] selftests: lib: return Kselftest Skip code for skipped tests

When lib test(s) is skipped because of unmet dependencies and/or unsupported configuration, it returns non-zero value hich is treated as a fail by the Kselftest framework. This leads to false negative result even when the test could not be run. Change it to return kselftest skip code when a test

[PATCH 16/24] selftests: lib: return Kselftest Skip code for skipped tests

When lib test(s) is skipped because of unmet dependencies and/or unsupported configuration, it returns non-zero value hich is treated as a fail by the Kselftest framework. This leads to false negative result even when the test could not be run. Change it to return kselftest skip code when a test

[PATCH 11/24] selftests: intel_pstate: return Kselftest Skip code for skipped tests

When intel_pstate test is skipped because of unmet dependencies and/or unsupported configuration, it returns 0 which is treated as a pass by the Kselftest framework. This leads to false positive result even when the test could not be run. Change it to return kselftest skip code when a test gets

[PATCH 12/24] selftests: ipc: return Kselftest Skip code for skipped tests

When ipc test is skipped because of unmet dependencies and/or unsupported configuration, it exits with error which is treated as a fail by the Kselftest framework. This leads to false negative result even when the test could not be run. Change it to return kselftest skip code when a test gets

[PATCH 15/24] selftests: lib: add prime_numbers.sh test to Makefile

prime_numbers.sh is not included in TEST_PROGS. Add it. Signed-off-by: Shuah Khan (Samsung OSG) --- tools/testing/selftests/lib/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/testing/selftests/lib/Makefile

[PATCH 13/24] selftests: kmod: return Kselftest Skip code for skipped tests

When kmod test is skipped because of unmet dependencies and/or unsupported configuration, it returns 0 which is treated as a pass by the Kselftest framework. This leads to false positive result even when the test could not be run. It returns fail in some cases when test is skipped. Either way, it

[PATCH 11/24] selftests: intel_pstate: return Kselftest Skip code for skipped tests

When intel_pstate test is skipped because of unmet dependencies and/or unsupported configuration, it returns 0 which is treated as a pass by the Kselftest framework. This leads to false positive result even when the test could not be run. Change it to return kselftest skip code when a test gets

[PATCH 12/24] selftests: ipc: return Kselftest Skip code for skipped tests

When ipc test is skipped because of unmet dependencies and/or unsupported configuration, it exits with error which is treated as a fail by the Kselftest framework. This leads to false negative result even when the test could not be run. Change it to return kselftest skip code when a test gets

[PATCH 15/24] selftests: lib: add prime_numbers.sh test to Makefile

prime_numbers.sh is not included in TEST_PROGS. Add it. Signed-off-by: Shuah Khan (Samsung OSG) --- tools/testing/selftests/lib/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/testing/selftests/lib/Makefile b/tools/testing/selftests/lib/Makefile index

[PATCH 13/24] selftests: kmod: return Kselftest Skip code for skipped tests

When kmod test is skipped because of unmet dependencies and/or unsupported configuration, it returns 0 which is treated as a pass by the Kselftest framework. This leads to false positive result even when the test could not be run. It returns fail in some cases when test is skipped. Either way, it

[PATCH 14/24] selftests: kvm: return Kselftest Skip code for skipped tests

When kvm test is skipped because of unmet dependencies and/or unsupported configuration, it exits with error which is treated as a fail by the Kselftest framework. This leads to false negative result even when the test could not be run. Change it to return kselftest skip code when a test gets

[PATCH 14/24] selftests: kvm: return Kselftest Skip code for skipped tests

When kvm test is skipped because of unmet dependencies and/or unsupported configuration, it exits with error which is treated as a fail by the Kselftest framework. This leads to false negative result even when the test could not be run. Change it to return kselftest skip code when a test gets

[PATCH 10/24] selftests: gpio: return Kselftest Skip code for skipped tests

When gpio test is skipped because of unmet dependencies and/or unsupported configuration, it exits with error which is treated as a fail by the Kselftest framework. This leads to false negative result even when the test could not be run. Change it to return kselftest skip code when a test gets

[PATCH 10/24] selftests: gpio: return Kselftest Skip code for skipped tests

When gpio test is skipped because of unmet dependencies and/or unsupported configuration, it exits with error which is treated as a fail by the Kselftest framework. This leads to false negative result even when the test could not be run. Change it to return kselftest skip code when a test gets

[PATCH 09/24] selftests: ftrace: return Kselftest Skip code for skipped tests

When ftrace test is skipped because of unmet dependencies and/or unsupported configuration, it returns 0 which is treated as a pass by the Kselftest framework. This leads to false positive result even when the test could not be run. Change it to return kselftest skip code when a test gets skipped

[PATCH 09/24] selftests: ftrace: return Kselftest Skip code for skipped tests

When ftrace test is skipped because of unmet dependencies and/or unsupported configuration, it returns 0 which is treated as a pass by the Kselftest framework. This leads to false positive result even when the test could not be run. Change it to return kselftest skip code when a test gets skipped

[PATCH 08/24] selftests: firmware: return Kselftest Skip code for skipped tests

When firmware test(s) get skipped because of unmet dependencies and/or unsupported configuration, it returns 0 which is treated as a pass by the Kselftest framework. This leads to false positive result even when the test could not be run. Change it to return kselftest skip code when a test gets

[PATCH 08/24] selftests: firmware: return Kselftest Skip code for skipped tests

When firmware test(s) get skipped because of unmet dependencies and/or unsupported configuration, it returns 0 which is treated as a pass by the Kselftest framework. This leads to false positive result even when the test could not be run. Change it to return kselftest skip code when a test gets

[PATCH 07/24] selftests: filesystems: return Kselftest Skip code for skipped tests

When devpts_pts test is skipped because of unmet dependencies and/or unsupported configuration, it exits with error which is treated as a fail by the Kselftest framework. This leads to false negative result even when the test could not be run. In another case, it returns pass for a skipped test

[PATCH 06/24] selftests: exec: return Kselftest Skip code for skipped tests

When execveat test is skipped because of unmet dependencies and/or unsupported configuration, it exits with error which is treated as a fail by the Kselftest framework. This leads to false negative result even when the test could not be run. Change it to return kselftest skip code when a test

[PATCH 07/24] selftests: filesystems: return Kselftest Skip code for skipped tests

When devpts_pts test is skipped because of unmet dependencies and/or unsupported configuration, it exits with error which is treated as a fail by the Kselftest framework. This leads to false negative result even when the test could not be run. In another case, it returns pass for a skipped test

[PATCH 06/24] selftests: exec: return Kselftest Skip code for skipped tests

When execveat test is skipped because of unmet dependencies and/or unsupported configuration, it exits with error which is treated as a fail by the Kselftest framework. This leads to false negative result even when the test could not be run. Change it to return kselftest skip code when a test

[PATCH 04/24] selftests: cpufreq: return Kselftest Skip code for skipped tests

When cpufreq test is skipped because of unmet dependencies and/or unsupported configuration, it exits with error which is treated as a fail by the Kselftest framework. This leads to false negative result even when the test could not be run. Change it to return kselftest skip code when a test gets

[PATCH 05/24] selftests: efivarfs: return Kselftest Skip code for skipped tests

When efivarfs test is skipped because of unmet dependencies and/or unsupported configuration, it returns 0 which is treated as a pass by the Kselftest framework. This leads to false positive result even when the test could not be run. Change it to return kselftest skip code when a test gets

[PATCH 04/24] selftests: cpufreq: return Kselftest Skip code for skipped tests

When cpufreq test is skipped because of unmet dependencies and/or unsupported configuration, it exits with error which is treated as a fail by the Kselftest framework. This leads to false negative result even when the test could not be run. Change it to return kselftest skip code when a test gets

[PATCH 05/24] selftests: efivarfs: return Kselftest Skip code for skipped tests

When efivarfs test is skipped because of unmet dependencies and/or unsupported configuration, it returns 0 which is treated as a pass by the Kselftest framework. This leads to false positive result even when the test could not be run. Change it to return kselftest skip code when a test gets

[PATCH 03/24] selftests: cpu-hotplug: return Kselftest Skip code for skipped tests

When cpu-on-off-test is skipped because of unmet dependencies and/or unsupported configuration, it returns 0 which is treated as a pass by the Kselftest framework. This leads to false positive result even when the test could not be run. Change it to return kselftest skip code when a test gets

[PATCH 01/24] selftests: android: ion: return Kselftest Skip code for skipped tests

When ion test is skipped because of unmet dependencies and/or unsupported configuration, it returns 0 which is treated as a pass by the Kselftest framework. This leads to false positive result even when the test could not be run. Change it to return kselftest skip code when a test gets skipped to

[PATCH 02/24] selftests: breakpoints: return Kselftest Skip code for skipped tests

When step_after_suspend_test is skipped because of unmet dependencies and/or unsupported configuration, it exits with error which is treated as a fail by the Kselftest framework. This leads to false negative result even when the test could not be run. Change it to return kselftest skip code when

[PATCH 03/24] selftests: cpu-hotplug: return Kselftest Skip code for skipped tests

When cpu-on-off-test is skipped because of unmet dependencies and/or unsupported configuration, it returns 0 which is treated as a pass by the Kselftest framework. This leads to false positive result even when the test could not be run. Change it to return kselftest skip code when a test gets

[PATCH 01/24] selftests: android: ion: return Kselftest Skip code for skipped tests

When ion test is skipped because of unmet dependencies and/or unsupported configuration, it returns 0 which is treated as a pass by the Kselftest framework. This leads to false positive result even when the test could not be run. Change it to return kselftest skip code when a test gets skipped to

[PATCH 02/24] selftests: breakpoints: return Kselftest Skip code for skipped tests

When step_after_suspend_test is skipped because of unmet dependencies and/or unsupported configuration, it exits with error which is treated as a fail by the Kselftest framework. This leads to false negative result even when the test could not be run. Change it to return kselftest skip code when

Re: [PATCH v13 3/3] mm, powerpc, x86: introduce an additional vma bit for powerpc pkey

On Fri, May 04, 2018 at 03:57:33PM -0700, Dave Hansen wrote: > > diff --git a/fs/proc/task_mmu.c b/fs/proc/task_mmu.c > > index 0c9e392..3c7 100644 > > --- a/fs/proc/task_mmu.c > > +++ b/fs/proc/task_mmu.c > > @@ -679,6 +679,7 @@ static void show_smap_vma_flags(struct seq_file *m, > > struct

Re: [PATCH v13 3/3] mm, powerpc, x86: introduce an additional vma bit for powerpc pkey

On Fri, May 04, 2018 at 03:57:33PM -0700, Dave Hansen wrote: > > diff --git a/fs/proc/task_mmu.c b/fs/proc/task_mmu.c > > index 0c9e392..3c7 100644 > > --- a/fs/proc/task_mmu.c > > +++ b/fs/proc/task_mmu.c > > @@ -679,6 +679,7 @@ static void show_smap_vma_flags(struct seq_file *m, > > struct

*alloc API changes

Hi, After writing up this email, I think I don't like this idea, but I'm still curious to see what people think of the general observations... The number of permutations for our various allocation function is rather huge. Currently, it is: system or wrapper: kmem_cache_alloc, kmalloc, vmalloc,

*alloc API changes

Hi, After writing up this email, I think I don't like this idea, but I'm still curious to see what people think of the general observations... The number of permutations for our various allocation function is rather huge. Currently, it is: system or wrapper: kmem_cache_alloc, kmalloc, vmalloc,

Re: [v2] mm: access to uninitialized struct page

-Uytterhoeven/dt-bindings-can-rcar_can-Fix-R8A7796-SoC-name/20180504-154952' into devel-catchup-201805041701 git bisect bad 1deba87932c5d0adcffe63d8ce4847f39e864775 # 20:56 B 2Merge 'yhuang/fix_thp_swap' into devel-catchup-201805041701 git bisect good e0997365e1e89e8bc9f5ed4a58a6cd2500b58668

Re: [v2] mm: access to uninitialized struct page

-Uytterhoeven/dt-bindings-can-rcar_can-Fix-R8A7796-SoC-name/20180504-154952' into devel-catchup-201805041701 git bisect bad 1deba87932c5d0adcffe63d8ce4847f39e864775 # 20:56 B 2Merge 'yhuang/fix_thp_swap' into devel-catchup-201805041701 git bisect good e0997365e1e89e8bc9f5ed4a58a6cd2500b58668

Re: [PATCH v2 net-next 2/4] net: add skeleton of bpfilter kernel module

On Thu, May 03, 2018 at 03:23:55PM +0100, Edward Cree wrote: > On 03/05/18 05:36, Alexei Starovoitov wrote: > > bpfilter.ko consists of bpfilter_kern.c (normal kernel module code) > > and user mode helper code that is embedded into bpfilter.ko > > > > The steps to build bpfilter.ko are the

Re: [PATCH v2 net-next 2/4] net: add skeleton of bpfilter kernel module

On Thu, May 03, 2018 at 03:23:55PM +0100, Edward Cree wrote: > On 03/05/18 05:36, Alexei Starovoitov wrote: > > bpfilter.ko consists of bpfilter_kern.c (normal kernel module code) > > and user mode helper code that is embedded into bpfilter.ko > > > > The steps to build bpfilter.ko are the

Re: [PATCH 1/3] spi: meson-axg: support MAX 80M clock

On Fri, May 04, 2018 at 09:56:10AM +0800, Yixun Lan wrote: > Here I only introduce the dt compatible data to differentiate the > old/new controller, the compatible name is not changed, and none of the > property is introduced. Right, sorry - this bit is fine. signature.asc Description: PGP

Re: [PATCH 1/3] spi: meson-axg: support MAX 80M clock

On Fri, May 04, 2018 at 09:56:10AM +0800, Yixun Lan wrote: > Here I only introduce the dt compatible data to differentiate the > old/new controller, the compatible name is not changed, and none of the > property is introduced. Right, sorry - this bit is fine. signature.asc Description: PGP

Re: rcu-bh design

On Fri, May 4, 2018 at 4:42 PM Paul E. McKenney wrote: [..] > > Say that the tracepoint code is buggy and for some reason a > > call_srcu wasn't done. For example, say the hypothetical bug I'm > > taking about is in tracepoint_remove_func which called the > >

Re: rcu-bh design

On Fri, May 4, 2018 at 4:42 PM Paul E. McKenney wrote: [..] > > Say that the tracepoint code is buggy and for some reason a > > call_srcu wasn't done. For example, say the hypothetical bug I'm > > taking about is in tracepoint_remove_func which called the > > rcu_assign_pointer, but didn't call

Re: Oops on the system startup in the function part_in_flight()

Hello, I am trying to bisect a pktgen related performance regression that appears to be between the 4.13 and 4.14 kernels. But, my system keeps crashing due to part_in_flight oops so bisecting is not going well. It looks like this oops was fixed, but the link to the patch in the email is no

Re: Oops on the system startup in the function part_in_flight()

Hello, I am trying to bisect a pktgen related performance regression that appears to be between the 4.13 and 4.14 kernels. But, my system keeps crashing due to part_in_flight oops so bisecting is not going well. It looks like this oops was fixed, but the link to the patch in the email is no

Re: [PATCH] elf: don't hash userspace addresses

Alexey Dobriyan wrote: > Signed-off-by: Alexey Dobriyan > --- > > fs/binfmt_elf.c |4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > --- a/fs/binfmt_elf.c > +++ b/fs/binfmt_elf.c > @@ -379,8 +379,8 @@ static unsigned long elf_map(struct file *filep,

Re: [PATCH] elf: don't hash userspace addresses

Alexey Dobriyan wrote: > Signed-off-by: Alexey Dobriyan > --- > > fs/binfmt_elf.c |4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > --- a/fs/binfmt_elf.c > +++ b/fs/binfmt_elf.c > @@ -379,8 +379,8 @@ static unsigned long elf_map(struct file *filep, unsigned > long addr, > >

[GIT PULL] remoteproc and rpmsg fixes for v4.17

The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338: Linux 4.17-rc1 (2018-04-15 18:24:20 -0700) are available in the Git repository at: git://github.com/andersson/remoteproc tags/rproc-v4.17-1 for you to fetch changes up to 93dd4e73c0d9cc32f835d76a54257020b0bfc75a:

[GIT PULL] remoteproc and rpmsg fixes for v4.17

The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338: Linux 4.17-rc1 (2018-04-15 18:24:20 -0700) are available in the Git repository at: git://github.com/andersson/remoteproc tags/rproc-v4.17-1 for you to fetch changes up to 93dd4e73c0d9cc32f835d76a54257020b0bfc75a:

Re: [PATCH V3] Input: pm8941-pwrkey: add resin key capabilities

Hi Tirupathi, On Fri, Mar 23, 2018 at 11:53:12AM +0530, Tirupathi Reddy wrote: > Add resin key support to handle different types of key events > defined in different platforms. > > Signed-off-by: Tirupathi Reddy > --- > .../bindings/input/qcom,pm8941-pwrkey.txt

Re: [PATCH V3] Input: pm8941-pwrkey: add resin key capabilities

Hi Tirupathi, On Fri, Mar 23, 2018 at 11:53:12AM +0530, Tirupathi Reddy wrote: > Add resin key support to handle different types of key events > defined in different platforms. > > Signed-off-by: Tirupathi Reddy > --- > .../bindings/input/qcom,pm8941-pwrkey.txt | 32 + >

Re: [PATCH V2 2/5] X86: Hyper-V: Enable IPI enlightenments

Hi Srinivasan, I love your patch! Yet something to improve: [auto build test ERROR on v4.17-rc3] [also build test ERROR on next-20180504] [cannot apply to tip/x86/core] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https

Re: [PATCH V2 2/5] X86: Hyper-V: Enable IPI enlightenments

Hi Srinivasan, I love your patch! Yet something to improve: [auto build test ERROR on v4.17-rc3] [also build test ERROR on next-20180504] [cannot apply to tip/x86/core] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https

[PATCH] proc: test /proc/*/fd a bit (+ PF_KTHREAD is ABI!)

* Test lookup in /proc/self/fd. "map_files" lookup story showed that lookup is not that simple. * Test that all those symlinks open the same file. Check with (st_dev, st_info). * Test that kernel threads do not have anything in their /proc/*/fd/ directory. Now this is where things get

Re: [PATCH v3 3/3] sh: add the sh_ prefix to early platform symbols

On Fri, May 4, 2018 at 9:27 AM, Bartosz Golaszewski wrote: > From: Bartosz Golaszewski > > Old early platform device support is now sh-specific. Before moving on > to implementing new early platform framework based on real platform > devices, prefix all

[PATCH] proc: test /proc/*/fd a bit (+ PF_KTHREAD is ABI!)

* Test lookup in /proc/self/fd. "map_files" lookup story showed that lookup is not that simple. * Test that all those symlinks open the same file. Check with (st_dev, st_info). * Test that kernel threads do not have anything in their /proc/*/fd/ directory. Now this is where things get

Re: [PATCH v3 3/3] sh: add the sh_ prefix to early platform symbols

On Fri, May 4, 2018 at 9:27 AM, Bartosz Golaszewski wrote: > From: Bartosz Golaszewski > > Old early platform device support is now sh-specific. Before moving on > to implementing new early platform framework based on real platform > devices, prefix all early platform symbols with 'sh_'. > >

Re: [PATCH v3 1/3] clocksource: timer-ti-dm: remove the early platform driver registration

On Fri, May 4, 2018 at 9:27 AM, Bartosz Golaszewski wrote: > From: Bartosz Golaszewski > > This driver is no longer used as an early platform driver. Remove the > registration macro. > > Signed-off-by: Bartosz Golaszewski

Re: [PATCH v3 1/3] clocksource: timer-ti-dm: remove the early platform driver registration

On Fri, May 4, 2018 at 9:27 AM, Bartosz Golaszewski wrote: > From: Bartosz Golaszewski > > This driver is no longer used as an early platform driver. Remove the > registration macro. > > Signed-off-by: Bartosz Golaszewski Acked-by: Arnd Bergmann

[RESEND PATCH] pinctrl: qcom: fix wrong pull status display for no_keeper SoC

From: Clément Péron DebugFS strings about pin pull status for no_keeper SoC are wrong Fix this by adding a different string array for no_keeper SoC Signed-off-by: Clément Péron Signed-off-by: Bjorn Andersson --- Hi

[RESEND PATCH] pinctrl: qcom: fix wrong pull status display for no_keeper SoC

From: Clément Péron DebugFS strings about pin pull status for no_keeper SoC are wrong Fix this by adding a different string array for no_keeper SoC Signed-off-by: Clément Péron Signed-off-by: Bjorn Andersson --- Hi Linus, Forwarding this patch which was posted to linux-arm-msm@ only. LGTM,

Re: Introducing a nanoMIPS port for Linux

On Fri, May 4, 2018 at 9:24 AM, James Hogan wrote: > On Thu, May 03, 2018 at 06:40:07PM -0400, Arnd Bergmann wrote: >> On Wed, May 2, 2018 at 5:51 PM, James Hogan wrote: >> >> While I haven't looked at the individual changes, I wonder whether >> it would be

Re: Introducing a nanoMIPS port for Linux

On Fri, May 4, 2018 at 9:24 AM, James Hogan wrote: > On Thu, May 03, 2018 at 06:40:07PM -0400, Arnd Bergmann wrote: >> On Wed, May 2, 2018 at 5:51 PM, James Hogan wrote: >> >> While I haven't looked at the individual changes, I wonder whether >> it would be useful to make this new ABI use 64-bit

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