From: Christian Brauner <christian@brauner.io>
To: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Cc: arnd@arndb.de, Christian Brauner <christian@brauner.io>
Subject: [GIT PULL] pidfd fixes for v5.2-rc4
Date: Wed, 5 Jun 2019 15:29:37 +0200 [thread overview]
Message-ID: <20190605132937.29438-1-christian@brauner.io> (raw)
Hi Linus,
This is a pull request containing three hopefully uncontroversial fixes:
The following changes since commit f2c7c76c5d0a443053e94adb9f0918fa2fb85c3a:
Linux 5.2-rc3 (2019-06-02 13:55:33 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/brauner/linux tags/pidfd-fixes-v5.2-rc4
for you to fetch changes up to 1fcd0eb356ad56c4e405f06e31dd9fde2109d5ab:
tests: fix pidfd-test compilation (2019-06-05 15:06:32 +0200)
The tag contains two small patches to the pidfd samples and test binaries
respectively. They were lacking appropriate ifdefines for
__NR_pidfd_send_signal and could hence lead to compilation errors when
__NR_pidfd_send_signal was not defined.
This was spotted on mips independently by Guenter Roeck (who was kind
enough to send a fix for the samples binary) and Arnd who spotted it in
linux-next.
Apart from these two patches, there's also a patch to update the comments
for the pidfd_send_signal() syscall which were slightly wrong/inconsistenly
worded.
Please consider pulling these changes from the signed pidfd-fixes-v5.2-rc4 tag.
Thanks!
Christian
----------------------------------------------------------------
pidfd fixes for v5.2-rc4
----------------------------------------------------------------
Christian Brauner (2):
signal: improve comments
tests: fix pidfd-test compilation
Guenter Roeck (1):
samples: fix pidfd-metadata compilation
kernel/signal.c | 11 +++++------
samples/pidfd/pidfd-metadata.c | 4 ++++
tools/testing/selftests/pidfd/pidfd_test.c | 4 ++++
3 files changed, 13 insertions(+), 6 deletions(-)
next reply other threads:[~2019-06-05 13:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 13:29 Christian Brauner [this message]
2019-06-05 21:05 ` pr-tracker-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190605132937.29438-1-christian@brauner.io \
--to=christian@brauner.io \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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®