* [GIT PULL] process fixes for v5.4-rc2
@ 2019-10-04 9:39 Christian Brauner
2019-10-04 17:24 ` Linus Torvalds
2019-10-04 18:25 ` pr-tracker-bot
0 siblings, 2 replies; 4+ messages in thread
From: Christian Brauner @ 2019-10-04 9:39 UTC (permalink / raw)
To: torvalds; +Cc: linux-kernel
Hi Linus,
/* Summary */
This pull request contains a couple of fixes:
- Fix pidfd selftest compilation (Shuah Kahn)
Due to a false linking instruction in the Makefile compilation for the
pidfd selftests would fail on some systems.
- Fix compilation for glibc on RISC-V systems (Seth Forshee)
In some scenarios linux/uapi/linux/sched.h is included where __ASSEMBLY__
is defined causing a build failure because struct clone_args was not
guarded by an #ifndef __ASSEMBLY__.
- Add missing clone3() and struct clone_args kernel-doc (Christian Brauner)
clone3() and struct clone_args were missing kernel-docs. (The goal is to
use kernel-doc for any function or type where it's worth it.)
For struct clone_args this also contains a comment about the fact that
it's versioned by size.
The following changes since commit 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c:
Linux 5.4-rc1 (2019-09-30 10:35:40 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/brauner/linux tags/for-linus-20191003
for you to fetch changes up to 78f6face5af344f12f4bd48b32faa6f499a06f36:
sched: add kernel-doc for struct clone_args (2019-10-03 21:19:29 +0200)
/* Testing */
All patches have seen exposure in linux-next and are based on v5.4-rc1.
/* Conflicts */
At the time of creating this PR no merge conflicts were reported from
linux-next.
Please consider pulling these changes from the signed for-linus-20191003 tag.
Thanks!
Christian
----------------------------------------------------------------
for-linus-20191003
----------------------------------------------------------------
Christian Brauner (2):
fork: add kernel-doc for clone3
sched: add kernel-doc for struct clone_args
Seth Forshee (1):
sched: Add __ASSEMBLY__ guards around struct clone_args
Shuah Khan (1):
selftests: pidfd: Fix undefined reference to pthread_create()
include/uapi/linux/sched.h | 28 ++++++++++++++++++++++++++--
kernel/fork.c | 11 +++++++++++
tools/testing/selftests/pidfd/Makefile | 2 +-
3 files changed, 38 insertions(+), 3 deletions(-)
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [GIT PULL] process fixes for v5.4-rc2
2019-10-04 9:39 [GIT PULL] process fixes for v5.4-rc2 Christian Brauner
@ 2019-10-04 17:24 ` Linus Torvalds
2019-10-04 17:38 ` Christian Brauner
2019-10-04 18:25 ` pr-tracker-bot
1 sibling, 1 reply; 4+ messages in thread
From: Linus Torvalds @ 2019-10-04 17:24 UTC (permalink / raw)
To: Christian Brauner; +Cc: Linux Kernel Mailing List
On Fri, Oct 4, 2019 at 2:40 AM Christian Brauner
<christian.brauner@ubuntu.com> wrote:
>
> This pull request contains a couple of fixes:
Pulled.
Small note: it is sad, and I'm ashamed of my life, but to me "process"
these days is about development process rather than about a group of
threads sharing a VM.
I know, I know. I feel like a (shudder) manager. But when I see a pull
request for "process fixes", my mind goes to documentation about our
processes for pull requests and sending patches etc.
You don't need to change anything in your life or emails - you've got
it right - but this just explains why your pull request is now labeled
"clone3/pidfd fixes" in my tree, and why it might be better to talk to
me about "treads" rather than processes.
Linus
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [GIT PULL] process fixes for v5.4-rc2
2019-10-04 17:24 ` Linus Torvalds
@ 2019-10-04 17:38 ` Christian Brauner
0 siblings, 0 replies; 4+ messages in thread
From: Christian Brauner @ 2019-10-04 17:38 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Linux Kernel Mailing List
On Fri, Oct 04, 2019 at 10:24:05AM -0700, Linus Torvalds wrote:
> On Fri, Oct 4, 2019 at 2:40 AM Christian Brauner
> <christian.brauner@ubuntu.com> wrote:
> >
> > This pull request contains a couple of fixes:
>
> Pulled.
>
> Small note: it is sad, and I'm ashamed of my life, but to me "process"
> these days is about development process rather than about a group of
> threads sharing a VM.
>
> I know, I know. I feel like a (shudder) manager. But when I see a pull
> request for "process fixes", my mind goes to documentation about our
> processes for pull requests and sending patches etc.
Well, there are an aweful lot of mails about development process
recently...
>
> You don't need to change anything in your life or emails - you've got
> it right - but this just explains why your pull request is now labeled
> "clone3/pidfd fixes" in my tree, and why it might be better to talk to
> me about "treads" rather than processes.
Noted. Next pr will be "thread".
Christian
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [GIT PULL] process fixes for v5.4-rc2
2019-10-04 9:39 [GIT PULL] process fixes for v5.4-rc2 Christian Brauner
2019-10-04 17:24 ` Linus Torvalds
@ 2019-10-04 18:25 ` pr-tracker-bot
1 sibling, 0 replies; 4+ messages in thread
From: pr-tracker-bot @ 2019-10-04 18:25 UTC (permalink / raw)
To: Christian Brauner; +Cc: torvalds, linux-kernel
The pull request you sent on Fri, 4 Oct 2019 11:39:47 +0200:
> git@gitolite.kernel.org:pub/scm/linux/kernel/git/brauner/linux tags/for-linus-20191003
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/af0622f6ae416f9ac340d6d632be9879805c294a
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/userdoc/prtracker
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2019-10-04 18:25 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-10-04 9:39 [GIT PULL] process fixes for v5.4-rc2 Christian Brauner
2019-10-04 17:24 ` Linus Torvalds
2019-10-04 17:38 ` Christian Brauner
2019-10-04 18:25 ` pr-tracker-bot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®