From: Christian Brauner <christian.brauner@ubuntu.com>
To: Dmitry Safonov <0x7f454c46@gmail.com>
Cc: Adrian Reber <areber@redhat.com>,
Eric Biederman <ebiederm@xmission.com>,
Pavel Emelyanov <ovzxemul@gmail.com>,
Jann Horn <jannh@google.com>, Oleg Nesterov <oleg@redhat.com>,
Andrei Vagin <avagin@gmail.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
linux-kernel@vger.kernel.org, Mike Rapoport <rppt@linux.ibm.com>,
Radostin Stoyanov <rstoyanov1@gmail.com>
Subject: Re: [PATCH v11 1/2] fork: extend clone3() to support setting a PID
Date: Fri, 15 Nov 2019 23:51:46 +0100 [thread overview]
Message-ID: <20191115225145.c6r5avibiluzxj3c@wittgenstein> (raw)
In-Reply-To: <fada5995-7fcc-7ca8-0933-4d0f52deef6e@gmail.com>
On Fri, Nov 15, 2019 at 04:54:06PM +0000, Dmitry Safonov wrote:
> On 11/15/19 12:36 PM, Adrian Reber wrote:
> [..]
> > Signed-off-by: Adrian Reber <areber@redhat.com>
> > Reviewed-by: Christian Brauner <christian.brauner@ubuntu.com>
>
> Reviewed-by: Dmitry Safonov <0x7f454c46@gmail.com>
>
> [though, I have 2 minor nits below]
>
> [..]
> > + * @set_tid: Pointer to an array of type *pid_t. The size
> > + * of the array is defined using @set_tid_size.
> > + * This array is used select PIDs/TIDs for newly
>
> /is used select/is used to select/s
I fixed this up while applying.
Thanks!
Christian
next prev parent reply other threads:[~2019-11-15 22:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 12:36 [PATCH v11 1/2] fork: extend clone3() to support setting a PID Adrian Reber
2019-11-15 12:36 ` [PATCH v11 2/2] selftests: add tests for clone3() with *set_tid Adrian Reber
2019-11-15 22:20 ` Andrei Vagin
2019-11-15 22:53 ` Christian Brauner
2019-11-18 1:46 ` Andrei Vagin
2019-11-18 7:42 ` Christian Brauner
2019-11-15 16:33 ` [PATCH v11 1/2] fork: extend clone3() to support setting a PID Oleg Nesterov
2019-11-15 16:54 ` Dmitry Safonov
2019-11-15 17:02 ` Dmitry Safonov
2019-11-15 22:51 ` Christian Brauner [this message]
2019-11-15 21:54 ` Andrei Vagin
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=20191115225145.c6r5avibiluzxj3c@wittgenstein \
--to=christian.brauner@ubuntu.com \
--cc=0x7f454c46@gmail.com \
--cc=areber@redhat.com \
--cc=avagin@gmail.com \
--cc=ebiederm@xmission.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=oleg@redhat.com \
--cc=ovzxemul@gmail.com \
--cc=rppt@linux.ibm.com \
--cc=rstoyanov1@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).