Re: [PATCH][V2] net: stmmac: ensure jumbo_frm error return is correctly checked for -ve value

From: Colin King Date: Mon, 5 Jun 2017 10:04:52 +0100 > From: Colin Ian King > > The current comparison of entry < 0 will never be true since entry is an > unsigned integer. Make entry an int to ensure -ve error return values > from the call

Re: [PATCH][V2] net: stmmac: ensure jumbo_frm error return is correctly checked for -ve value

From: Colin King Date: Mon, 5 Jun 2017 10:04:52 +0100 > From: Colin Ian King > > The current comparison of entry < 0 will never be true since entry is an > unsigned integer. Make entry an int to ensure -ve error return values > from the call to jumbo_frm are correctly being caught. > >

[PATCH 14/26] wait: Move changing of ptrace from wait_consider_task into wait_task_stopped

With the freeing and slaying of zombies moved earlier in wait_consider_task changing of the ptrace value only effects the clearing of notask_error and wait_task_stopped. Move the changing of ptrace into wait_task_stopped. The value of ptrace coming into the code clearing notask_error is left at

Re: [PATCH] ppp: mppe: Use vsnprintf extension %phN

From: Joe Perches Date: Mon, 5 Jun 2017 05:22:50 -0700 > Using this extension reduces the object size. > > $ size drivers/net/ppp/ppp_mppe.o* >text data bss dec hex filename >5683 216 859071713

[PATCH 14/26] wait: Move changing of ptrace from wait_consider_task into wait_task_stopped

With the freeing and slaying of zombies moved earlier in wait_consider_task changing of the ptrace value only effects the clearing of notask_error and wait_task_stopped. Move the changing of ptrace into wait_task_stopped. The value of ptrace coming into the code clearing notask_error is left at

Re: [PATCH] ppp: mppe: Use vsnprintf extension %phN

From: Joe Perches Date: Mon, 5 Jun 2017 05:22:50 -0700 > Using this extension reduces the object size. > > $ size drivers/net/ppp/ppp_mppe.o* >text data bss dec hex filename >5683 216 859071713 drivers/net/ppp/ppp_mppe.o.new >5808

[PATCH 20/26] wait: Don't pass the list to wait_consider_task

The list a task is found on is not really relevant to wait, so stop passing the list in and write the conditions in such a way as to not take the list into consideration. This is technically user visible due to __WNOTHREAD but is very unlikely to matter in practice. Signed-off-by: "Eric W.

[PATCH 11/26] wait: Properly implement __WCLONE handling in the presence of exec and ptrace

Rewrite the condition for what contitues a clone child. AKA a child that reports to it's parent using something other than SIGCHLD. If the parent has called exec since the child has started that child will alwasy report to it's parent with SIGCHLD. If the parent is only ptracing the child the

[PATCH 20/26] wait: Don't pass the list to wait_consider_task

The list a task is found on is not really relevant to wait, so stop passing the list in and write the conditions in such a way as to not take the list into consideration. This is technically user visible due to __WNOTHREAD but is very unlikely to matter in practice. Signed-off-by: "Eric W.

[PATCH 11/26] wait: Properly implement __WCLONE handling in the presence of exec and ptrace

Rewrite the condition for what contitues a clone child. AKA a child that reports to it's parent using something other than SIGCHLD. If the parent has called exec since the child has started that child will alwasy report to it's parent with SIGCHLD. If the parent is only ptracing the child the

[PATCH 21/26] wait: Optmize waitpid

Now that which list a task is found on does not matter there is no reason to walk the child lists for waitpid when task_pid can directly find the child. Add a new helper do_wait_pid that finds the target task via pid_task and verifies it is on one of the lists for the thread we are reaping. This

[PATCH 21/26] wait: Optmize waitpid

Now that which list a task is found on does not matter there is no reason to walk the child lists for waitpid when task_pid can directly find the child. Add a new helper do_wait_pid that finds the target task via pid_task and verifies it is on one of the lists for the thread we are reaping. This

[PATCH 19/26] wait: Simpler code for clearing notask_error in wait_consider_task

Start with reaping pending zombies and then return if there is nothing wait_task_consider can ever do with the task. What remains are living tasks and delayed child zombie thread group leaders waiting for their thread group to exit. Leaving something for WEXITED to find later. As long as

[PATCH 19/26] wait: Simpler code for clearing notask_error in wait_consider_task

Start with reaping pending zombies and then return if there is nothing wait_task_consider can ever do with the task. What remains are living tasks and delayed child zombie thread group leaders waiting for their thread group to exit. Leaving something for WEXITED to find later. As long as

[PATCH 13/26] wait: Remove unused delay_group_leader

Signed-off-by: "Eric W. Biederman" --- include/linux/sched/signal.h | 3 --- 1 file changed, 3 deletions(-) diff --git a/include/linux/sched/signal.h b/include/linux/sched/signal.h index c06d63b3a583..0cc626dd79a8 100644 --- a/include/linux/sched/signal.h +++

[PATCH 13/26] wait: Remove unused delay_group_leader

Signed-off-by: "Eric W. Biederman" --- include/linux/sched/signal.h | 3 --- 1 file changed, 3 deletions(-) diff --git a/include/linux/sched/signal.h b/include/linux/sched/signal.h index c06d63b3a583..0cc626dd79a8 100644 --- a/include/linux/sched/signal.h +++ b/include/linux/sched/signal.h @@

[PATCH 24/26] signal: In ptrace_stop improve identical signal detection

When two signals are generated make it the thread level signal that is possibly surpessed. The reasoning is that the group level signal always needs to be generated to report a group stop when that happens and it is possibly doing double duty as both the group level and the thread level signal.

[PATCH 24/26] signal: In ptrace_stop improve identical signal detection

When two signals are generated make it the thread level signal that is possibly surpessed. The reasoning is that the group level signal always needs to be generated to report a group stop when that happens and it is possibly doing double duty as both the group level and the thread level signal.

[PATCH 5/7] sh: Use lib/ashldi3,ashrdi3,lshrdi3}.c

These files are functionally identical to the shared copies that I recently added. Signed-off-by: Palmer Dabbelt Reviewed-by: Geert Uytterhoeven --- arch/sh/Kconfig | 3 +++ arch/sh/boot/compressed/Makefile | 6 +++---

Unify the various copies of libgcc into lib v2

Thanks to everyone who responded to my original patch set. I believe I've responded to everyone's comments. There have been a handful of changes since the original patch set: * The Kconfig names for the routines are now GENERIC_* instead of LIB_*. This matches the existing generic

[PATCH 5/7] sh: Use lib/ashldi3,ashrdi3,lshrdi3}.c

These files are functionally identical to the shared copies that I recently added. Signed-off-by: Palmer Dabbelt Reviewed-by: Geert Uytterhoeven --- arch/sh/Kconfig | 3 +++ arch/sh/boot/compressed/Makefile | 6 +++--- arch/sh/lib/Makefile | 4 +---

Unify the various copies of libgcc into lib v2

Thanks to everyone who responded to my original patch set. I believe I've responded to everyone's comments. There have been a handful of changes since the original patch set: * The Kconfig names for the routines are now GENERIC_* instead of LIB_*. This matches the existing generic

[PATCH 4/7] score: Use lib/{ashldi3,ashrdi3,cmpdi2,lshrdi3,ucmpdi2}.c

These files are functionally identical to the shared copies that I recently added. Signed-off-by: Palmer Dabbelt Reviewed-by: Geert Uytterhoeven --- arch/score/Kconfig | 5 + arch/score/lib/Makefile | 3 --- arch/score/lib/ashldi3.c | 46

[PATCH 4/7] score: Use lib/{ashldi3,ashrdi3,cmpdi2,lshrdi3,ucmpdi2}.c

These files are functionally identical to the shared copies that I recently added. Signed-off-by: Palmer Dabbelt Reviewed-by: Geert Uytterhoeven --- arch/score/Kconfig | 5 + arch/score/lib/Makefile | 3 --- arch/score/lib/ashldi3.c | 46

[PATCH 15/26] wait: Don't delay !ptrace_reparented leaders

When ptracing waitpid(pid) has two possible meanings. - Wait for the task with tid == pid to exit - Wait for the thread group with tgid == pid to exit Linux resolves this ambiguity by prefering the thread group interpretation if it is possible. As the exit of a thread group containing a task is

[PATCH 16/26] exit: Fix reporting a ptraced !reparented leader has exited

When a task exits and uses do_notify_parent to send tsk->exit_signal or SIGCHLD this has one of two possible meanings. - The ptraced task has exited - The thread group has exited Linux resolves this ambiguity by preferring the thread group exit interpretation if it is possible. As the exit of a

[PATCH 15/26] wait: Don't delay !ptrace_reparented leaders

When ptracing waitpid(pid) has two possible meanings. - Wait for the task with tid == pid to exit - Wait for the thread group with tgid == pid to exit Linux resolves this ambiguity by prefering the thread group interpretation if it is possible. As the exit of a thread group containing a task is

[PATCH 16/26] exit: Fix reporting a ptraced !reparented leader has exited

When a task exits and uses do_notify_parent to send tsk->exit_signal or SIGCHLD this has one of two possible meanings. - The ptraced task has exited - The thread group has exited Linux resolves this ambiguity by preferring the thread group exit interpretation if it is possible. As the exit of a

[PATCH 05/26] exit: Remove the pointless clearing of SIGPENDING in __exit_signal

Handling of signals does not happen once do_exit is called as a process never again exits from the kernel. So remove this ancient hold over from something else. Furthermore this is TIF_SIGPENDING on a zombie. Which will never be scheduled on a cpu again. Setting sigpending=0 was silly in 2.4

[PATCH 05/26] exit: Remove the pointless clearing of SIGPENDING in __exit_signal

Handling of signals does not happen once do_exit is called as a process never again exits from the kernel. So remove this ancient hold over from something else. Furthermore this is TIF_SIGPENDING on a zombie. Which will never be scheduled on a cpu again. Setting sigpending=0 was silly in 2.4

[PATCH 09/26] signal: Don't allow sending SIGKILL or SIGSTOP to init

Even to init SIGKILL and SIGSTOP are alwasys delivered if they are sent, so don't allow tracing an init task allow them. Signed-off-by: "Eric W. Biederman" --- kernel/signal.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/kernel/signal.c

[PATCH 09/26] signal: Don't allow sending SIGKILL or SIGSTOP to init

Even to init SIGKILL and SIGSTOP are alwasys delivered if they are sent, so don't allow tracing an init task allow them. Signed-off-by: "Eric W. Biederman" --- kernel/signal.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/kernel/signal.c b/kernel/signal.c index

[PATCH 10/26] ptrace: Simplify ptrace_detach & exit_ptrace

Call __ptrace_unlink not __ptrace_detach. As it is guaranteed that ptrace_detach will never be called on a process that has or may exit. Rename __ptrace_detach __exit_ptrace as exit_ptrace is now it's only caller and the corrected name is less confusing. Signed-off-by: "Eric W. Biederman"

[PATCH 10/26] ptrace: Simplify ptrace_detach & exit_ptrace

Call __ptrace_unlink not __ptrace_detach. As it is guaranteed that ptrace_detach will never be called on a process that has or may exit. Rename __ptrace_detach __exit_ptrace as exit_ptrace is now it's only caller and the corrected name is less confusing. Signed-off-by: "Eric W. Biederman" ---

[PATCH 08/26] exit: Make the runqueue rcu safe

Add a rcu_usage to task_struct and use it to reuse the delayed rcu put logic from release_task in finish_task_switch. This guarantees that there will be an rcu interval before usage drops to zero for any task on the run queue. Making it safe to unconditionally call get_task_struct in a rcu

[PATCH 08/26] exit: Make the runqueue rcu safe

Add a rcu_usage to task_struct and use it to reuse the delayed rcu put logic from release_task in finish_task_switch. This guarantees that there will be an rcu interval before usage drops to zero for any task on the run queue. Making it safe to unconditionally call get_task_struct in a rcu

[PATCH 04/26] signal: Make group_send_sig_info static

It has no users outside of kernel/signal.c Signed-off-by: "Eric W. Biederman" --- include/linux/signal.h | 1 - kernel/signal.c| 1 + 2 files changed, 1 insertion(+), 1 deletion(-) diff --git a/include/linux/signal.h b/include/linux/signal.h index

[PATCH 04/26] signal: Make group_send_sig_info static

It has no users outside of kernel/signal.c Signed-off-by: "Eric W. Biederman" --- include/linux/signal.h | 1 - kernel/signal.c| 1 + 2 files changed, 1 insertion(+), 1 deletion(-) diff --git a/include/linux/signal.h b/include/linux/signal.h index 1f5a16620693..f1b296a5e537 100644 ---

[PATCH 03/26] signal: Do not perform permission checks when sending pdeath_signal

This fixes and old old regression. When Roland switched from sending pdeath_signal with send_sig() to send_group_sig_info it gained a permission check, and started taking the tasklist lock. Roland earlier fixed the double taking of the tasklist lock in 3f2a0d1df938 ("[PATCH] fix pdeath_signal

[PATCH 03/26] signal: Do not perform permission checks when sending pdeath_signal

This fixes and old old regression. When Roland switched from sending pdeath_signal with send_sig() to send_group_sig_info it gained a permission check, and started taking the tasklist lock. Roland earlier fixed the double taking of the tasklist lock in 3f2a0d1df938 ("[PATCH] fix pdeath_signal

[PATCH 06/26] rlimit: Remove unnecessary grab of tasklist_lock

There is no reason to take the tasklist lock here. The sighand structure is never referenced and and tsk->signal is guaranteed to stick around until tsk is freed. Further update_rlimit_cpu does not need the tasklist_lock. And the rlim_lock is used to guarantee mutual exclusion. Signed-off-by:

[PATCH 07/26] pidns: Improve the error handling in alloc_pid

Cause any failure to allocate pid 1 to permanently disable pid allocations for the pid namespace. Before the pid becomes pid 1 there ns->last_pid and other state remains unchanged so it is safe to try again... Signed-off-by: "Eric W. Biederman" --- kernel/pid.c | 8

[PATCH 06/26] rlimit: Remove unnecessary grab of tasklist_lock

There is no reason to take the tasklist lock here. The sighand structure is never referenced and and tsk->signal is guaranteed to stick around until tsk is freed. Further update_rlimit_cpu does not need the tasklist_lock. And the rlim_lock is used to guarantee mutual exclusion. Signed-off-by:

[PATCH 07/26] pidns: Improve the error handling in alloc_pid

Cause any failure to allocate pid 1 to permanently disable pid allocations for the pid namespace. Before the pid becomes pid 1 there ns->last_pid and other state remains unchanged so it is safe to try again... Signed-off-by: "Eric W. Biederman" --- kernel/pid.c | 8 +--- 1 file changed, 5

[PATCH 02/26] cgroup: Don't open code tasklist_empty()

Signed-off-by: "Eric W. Biederman" --- kernel/cgroup/cgroup.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/cgroup/cgroup.c b/kernel/cgroup/cgroup.c index c3c9a0e1b3c9..4b7d66cf8914 100644 --- a/kernel/cgroup/cgroup.c +++

[PATCH 02/26] cgroup: Don't open code tasklist_empty()

Signed-off-by: "Eric W. Biederman" --- kernel/cgroup/cgroup.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/cgroup/cgroup.c b/kernel/cgroup/cgroup.c index c3c9a0e1b3c9..4b7d66cf8914 100644 --- a/kernel/cgroup/cgroup.c +++ b/kernel/cgroup/cgroup.c @@ -4440,7 +4440,7

[PATCH 1/7] lib: Add shared copies of some GCC library routines

Many ports (m32r, microblaze, mips, parisc, score, and sparc) use functionally identical copies of various GCC library routine files, which came up as we were submitting the RISC-V port (which also uses some of these). This patch adds a new copy of these library routine files, which are

[PATCH 01/26] alpha: Remove unused TASK_GROUP_LEADER

This definition is for assembly code and no assembly code uses it. Remove the definition so that when making future changes we don't have to worry if alpha assembly code uses task->group_leader. Signed-off-by: "Eric W. Biederman" --- arch/alpha/kernel/asm-offsets.c | 1 -

[PATCH 6/7] sparc: Use lib/{cmpdi2,ucmpdi2}.c

These files are functionally identical to the shared copies that I recently added. Signed-off-by: Palmer Dabbelt Reviewed-by: Geert Uytterhoeven --- arch/sparc/Kconfig | 2 ++ arch/sparc/lib/Makefile | 4 ++-- arch/sparc/lib/cmpdi2.c | 27

[PATCH 1/7] lib: Add shared copies of some GCC library routines

Many ports (m32r, microblaze, mips, parisc, score, and sparc) use functionally identical copies of various GCC library routine files, which came up as we were submitting the RISC-V port (which also uses some of these). This patch adds a new copy of these library routine files, which are

[PATCH 01/26] alpha: Remove unused TASK_GROUP_LEADER

This definition is for assembly code and no assembly code uses it. Remove the definition so that when making future changes we don't have to worry if alpha assembly code uses task->group_leader. Signed-off-by: "Eric W. Biederman" --- arch/alpha/kernel/asm-offsets.c | 1 - 1 file changed, 1

[PATCH 6/7] sparc: Use lib/{cmpdi2,ucmpdi2}.c

These files are functionally identical to the shared copies that I recently added. Signed-off-by: Palmer Dabbelt Reviewed-by: Geert Uytterhoeven --- arch/sparc/Kconfig | 2 ++ arch/sparc/lib/Makefile | 4 ++-- arch/sparc/lib/cmpdi2.c | 27 ---

[PATCH 2/7] m32r: Use lib/ucmpdi2.c

These files are functionally identical to the shared copies that I recently added. Signed-off-by: Palmer Dabbelt Reviewed-by: Geert Uytterhoeven --- arch/m32r/Kconfig | 1 + arch/m32r/lib/Makefile | 3 +-- arch/m32r/lib/libgcc.h | 23

Applied "regmap: make LZO cache optional" to the regmap tree

The patch regmap: make LZO cache optional has been applied to the regmap tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.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 to Linus

[PATCH 2/7] m32r: Use lib/ucmpdi2.c

These files are functionally identical to the shared copies that I recently added. Signed-off-by: Palmer Dabbelt Reviewed-by: Geert Uytterhoeven --- arch/m32r/Kconfig | 1 + arch/m32r/lib/Makefile | 3 +-- arch/m32r/lib/libgcc.h | 23 --- arch/m32r/lib/ucmpdi2.c |

Applied "regmap: make LZO cache optional" to the regmap tree

The patch regmap: make LZO cache optional has been applied to the regmap tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.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 to Linus

Applied "spi: davinci: Fix compilation warning." to the spi tree

The patch spi: davinci: Fix compilation warning. has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.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 to Linus

Applied "spi: davinci: Fix compilation warning." to the spi tree

The patch spi: davinci: Fix compilation warning. has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.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 to Linus

Applied "spi: davinci: Handle return value of clk_prepare_enable" to the spi tree

The patch spi: davinci: Handle return value of clk_prepare_enable has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and

Applied "spi: davinci: Handle return value of clk_prepare_enable" to the spi tree

The patch spi: davinci: Handle return value of clk_prepare_enable has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and

Applied "spi: imx: Nothing to do in setupxfer when transfer is NULL" to the spi tree

The patch spi: imx: Nothing to do in setupxfer when transfer is NULL has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours)

Applied "spi: imx: Nothing to do in setupxfer when transfer is NULL" to the spi tree

The patch spi: imx: Nothing to do in setupxfer when transfer is NULL has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours)

Re: [PATCH 4/7] RISC-V: arch/riscv/include

On Tue, 06 Jun 2017 01:54:23 PDT (-0700), Arnd Bergmann wrote: > On Tue, Jun 6, 2017 at 6:56 AM, Palmer Dabbelt wrote: >> On Thu, 01 Jun 2017 02:00:22 PDT (-0700), Arnd Bergmann wrote: >>> On Thu, Jun 1, 2017 at 2:56 AM, Palmer Dabbelt wrote: On Tue,

Re: [PATCH 4/7] RISC-V: arch/riscv/include

On Tue, 06 Jun 2017 01:54:23 PDT (-0700), Arnd Bergmann wrote: > On Tue, Jun 6, 2017 at 6:56 AM, Palmer Dabbelt wrote: >> On Thu, 01 Jun 2017 02:00:22 PDT (-0700), Arnd Bergmann wrote: >>> On Thu, Jun 1, 2017 at 2:56 AM, Palmer Dabbelt wrote: On Tue, 23 May 2017 05:55:15 PDT (-0700), Arnd

Applied "spi: imx: Drop unnecessary check" to the spi tree

The patch spi: imx: Drop unnecessary check has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.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 to Linus during the

Applied "spi: imx: Drop unnecessary check" to the spi tree

The patch spi: imx: Drop unnecessary check has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.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 to Linus during the

Applied "spi: imx: drop bogus unnecessary dma config" to the spi tree

The patch spi: imx: drop bogus unnecessary dma config has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.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 to Linus

Applied "spi: imx: put struct spi_imx_config members into driver private struct" to the spi tree

The patch spi: imx: put struct spi_imx_config members into driver private struct has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next

Applied "spi: imx: drop bogus unnecessary dma config" to the spi tree

The patch spi: imx: drop bogus unnecessary dma config has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.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 to Linus

Applied "spi: imx: put struct spi_imx_config members into driver private struct" to the spi tree

The patch spi: imx: put struct spi_imx_config members into driver private struct has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next

[PATCH 00/26] Fixing wait, exit, ptrace, exec, and CLONE_THREAD

All, I am posting this patches in the hope of some review of the strategy I am taking and to let the individual patches be reviewed. The intersection of wait, exit, ptrace, exec, and CLONE_THREAD does not work correctly in the linux kernel. An easy entry point into seeing the problem is that

[PATCH 00/26] Fixing wait, exit, ptrace, exec, and CLONE_THREAD

All, I am posting this patches in the hope of some review of the strategy I am taking and to let the individual patches be reviewed. The intersection of wait, exit, ptrace, exec, and CLONE_THREAD does not work correctly in the linux kernel. An easy entry point into seeing the problem is that

Applied "spi: mediatek: Add bindings for mediatek MT7622 soc platform" to the spi tree

The patch spi: mediatek: Add bindings for mediatek MT7622 soc platform has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours)

Applied "spi: imx: rename 'bpw' variables" to the spi tree

The patch spi: imx: rename 'bpw' variables has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.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 to Linus during the

Applied "spi: mediatek: Add bindings for mediatek MT7622 soc platform" to the spi tree

The patch spi: mediatek: Add bindings for mediatek MT7622 soc platform has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours)

Applied "spi: imx: rename 'bpw' variables" to the spi tree

The patch spi: imx: rename 'bpw' variables has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.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 to Linus during the

Applied "spi: imx: remove bytes_per_word from private driver struct" to the spi tree

The patch spi: imx: remove bytes_per_word from private driver struct has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours)

Applied "spi: imx: remove bytes_per_word from private driver struct" to the spi tree

The patch spi: imx: remove bytes_per_word from private driver struct has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours)

Applied "ASoC: atmel: tse850: fix off-by-one in the "ANA" enumeration count" to the asoc tree

The patch ASoC: atmel: tse850: fix off-by-one in the "ANA" enumeration count has been applied to the asoc tree at git://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

Applied "ASoC: atmel: tse850: fix off-by-one in the "ANA" enumeration count" to the asoc tree

The patch ASoC: atmel: tse850: fix off-by-one in the "ANA" enumeration count has been applied to the asoc tree at git://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

Applied "ASoC: Intel: sst: Delete sst_shim_regs64; saved regs are never used" to the asoc tree

The patch ASoC: Intel: sst: Delete sst_shim_regs64; saved regs are never used has been applied to the asoc tree at git://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

Applied "ASoC: Intel: sst: Delete sst_shim_regs64; saved regs are never used" to the asoc tree

The patch ASoC: Intel: sst: Delete sst_shim_regs64; saved regs are never used has been applied to the asoc tree at git://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

Re: [RESEND PATCH V7 5/7] regulator: da9061: BUCK and LDO regulator driver

On Tue, May 30, 2017 at 10:17:59AM +0100, Lee Jones wrote: > On Wed, 24 May 2017, Mark Brown wrote: > > On Wed, May 24, 2017 at 09:32:43AM +0100, Lee Jones wrote: > > > Plan is to push this through the MFD tree. > > Great, thanks. > Just taking a look at this now. It looks like the

Re: [RESEND PATCH V7 5/7] regulator: da9061: BUCK and LDO regulator driver

On Tue, May 30, 2017 at 10:17:59AM +0100, Lee Jones wrote: > On Wed, 24 May 2017, Mark Brown wrote: > > On Wed, May 24, 2017 at 09:32:43AM +0100, Lee Jones wrote: > > > Plan is to push this through the MFD tree. > > Great, thanks. > Just taking a look at this now. It looks like the

Re: [PATCH v2 3/4] net: macb: macb.c changed to macb_main.c

From: Richard Cochran Date: Tue, 6 Jun 2017 20:39:33 +0200 > On Fri, Jun 02, 2017 at 03:27:41PM +0100, Rafal Ozieblo wrote: >> drivers/net/ethernet/cadence/macb.c | 3568 >> -- >> drivers/net/ethernet/cadence/macb_main.c | 3568 >>

Re: [PATCH v2 3/4] net: macb: macb.c changed to macb_main.c

From: Richard Cochran Date: Tue, 6 Jun 2017 20:39:33 +0200 > On Fri, Jun 02, 2017 at 03:27:41PM +0100, Rafal Ozieblo wrote: >> drivers/net/ethernet/cadence/macb.c | 3568 >> -- >> drivers/net/ethernet/cadence/macb_main.c | 3568 >>

Re: [PATCH 0/3] move visorbus out of staging to drivers/virt/visorbus

On Tue, Jun 06, 2017 at 06:20:17PM +, Kershner, David A wrote: > > > > -Original Message- > > From: Greg KH [mailto:gre...@linuxfoundation.org] > > Sent: Tuesday, June 6, 2017 11:06 AM > > To: Kershner, David A > > Cc: cor...@lwn.net; t...@linutronix.de;

Re: [PATCH 0/3] move visorbus out of staging to drivers/virt/visorbus

On Tue, Jun 06, 2017 at 06:20:17PM +, Kershner, David A wrote: > > > > -Original Message- > > From: Greg KH [mailto:gre...@linuxfoundation.org] > > Sent: Tuesday, June 6, 2017 11:06 AM > > To: Kershner, David A > > Cc: cor...@lwn.net; t...@linutronix.de; mi...@kernel.org;

Re: [PATCH 1/3] dt-bindings: spi: mediatek: Add bindings for mediatek MT7622 soc platform

On Fri, Jun 02, 2017 at 03:18:41PM +0800, Leilk Liu wrote: > This patch adds a DT binding documentation for the MT7622 soc. Please submit patches using subject lines reflecting the style for the subsystem. This makes it easier for people to identify relevant patches. Look at what existing

Re: [PATCH 1/3] dt-bindings: spi: mediatek: Add bindings for mediatek MT7622 soc platform

On Fri, Jun 02, 2017 at 03:18:41PM +0800, Leilk Liu wrote: > This patch adds a DT binding documentation for the MT7622 soc. Please submit patches using subject lines reflecting the style for the subsystem. This makes it easier for people to identify relevant patches. Look at what existing

Re: [PATCH 2/3] spi: mediatek: support adjust register define

On Fri, Jun 02, 2017 at 03:18:42PM +0800, Leilk Liu wrote: > + /* some IC design adjust register define */ > + bool adjust_reg; Can we have a name that's more specific to the particular quirk please? The current name will get confusing if some future chip also needs slightly different

Re: [PATCH 2/3] spi: mediatek: support adjust register define

On Fri, Jun 02, 2017 at 03:18:42PM +0800, Leilk Liu wrote: > + /* some IC design adjust register define */ > + bool adjust_reg; Can we have a name that's more specific to the particular quirk please? The current name will get confusing if some future chip also needs slightly different

Re: [PATCH 2/3] fs/locks: Remove fl_nspid

On 6 Jun 2017, at 14:25, Jeff Layton wrote: On Tue, 2017-06-06 at 14:00 -0400, Jeff Layton wrote: On Tue, 2017-06-06 at 13:19 -0400, Benjamin Coddington wrote: Since commit c69899a17ca4 "NFSv4: Update of VFS byte range lock must be atomic with the stateid update", NFSv4 has been inserting

Re: [PATCH 2/3] fs/locks: Remove fl_nspid

On 6 Jun 2017, at 14:25, Jeff Layton wrote: On Tue, 2017-06-06 at 14:00 -0400, Jeff Layton wrote: On Tue, 2017-06-06 at 13:19 -0400, Benjamin Coddington wrote: Since commit c69899a17ca4 "NFSv4: Update of VFS byte range lock must be atomic with the stateid update", NFSv4 has been inserting

Re: [RFC 2/3] misc: Add w2sg0004 (gps receiver) power control driver

> Am 31.05.2017 um 01:09 schrieb Rob Herring : > > On Sun, May 21, 2017 at 12:44:03PM +0200, H. Nikolaus Schaller wrote: >> Add driver for Wi2Wi W2SG0004/84 GPS module connected through uart. >> >> Use serdev API hooks to monitor and forward the UART traffic to /dev/BTn >> and

Re: [RFC 2/3] misc: Add w2sg0004 (gps receiver) power control driver

> Am 31.05.2017 um 01:09 schrieb Rob Herring : > > On Sun, May 21, 2017 at 12:44:03PM +0200, H. Nikolaus Schaller wrote: >> Add driver for Wi2Wi W2SG0004/84 GPS module connected through uart. >> >> Use serdev API hooks to monitor and forward the UART traffic to /dev/BTn >> and turn on/off the

Re: [RFC 0/3] misc: new serdev based drivers for w2sg00x4 GPS module and w2cbw003 wifi/bluetooth

Hi Rob, thanks for all the comments. > Am 25.05.2017 um 14:48 schrieb Rob Herring : > > On Tue, May 23, 2017 at 8:49 AM, H. Nikolaus Schaller > wrote: >> Hi Rob, >> >>> Am 23.05.2017 um 15:10 schrieb Rob Herring : >>> >>> +Marcel >>

Re: [RFC 0/3] misc: new serdev based drivers for w2sg00x4 GPS module and w2cbw003 wifi/bluetooth

Hi Rob, thanks for all the comments. > Am 25.05.2017 um 14:48 schrieb Rob Herring : > > On Tue, May 23, 2017 at 8:49 AM, H. Nikolaus Schaller > wrote: >> Hi Rob, >> >>> Am 23.05.2017 um 15:10 schrieb Rob Herring : >>> >>> +Marcel >> >> Good! >> >> Hm. Well: >> >> root@letux:~# hciconfig

Re: [PATCH 1/3] regmap: Add 1-Wire bus support

On Fri, Jun 02, 2017 at 10:06:27AM +0300, Alex A. Mihaylov wrote: > Add basic support regmap (register map access) API for 1-Wire bus Applied, thanks. I created a signed tag for the other two patches to use: The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6: Linux

Re: [PATCH 1/3] regmap: Add 1-Wire bus support

On Fri, Jun 02, 2017 at 10:06:27AM +0300, Alex A. Mihaylov wrote: > Add basic support regmap (register map access) API for 1-Wire bus Applied, thanks. I created a signed tag for the other two patches to use: The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6: Linux

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