From: Robin Naccari <robianna1973@icloud.com>
To: robianna1973@icloud.com
Cc: christian.brauner@ubuntu.com, containers@lists.linux.dev,
gscrivan@redhat.com, keescook@chromium.org,
linux-kernel@vger.kernel.org, luto@kernel.org,
mauricio@kinvolk.io, mic@linux.microsoft.com, rodrigo@kinvolk.io,
tycho@tycho.pizza
Subject: Re: [PATCH v2 3/4] seccomp: Support atomic "addfd + send reply"
Date: Mon, 18 Jul 2022 19:11:43 -0700 [thread overview]
Message-ID: <197A77C8-41B4-43E9-9779-CA68F39FD92E@icloud.com> (raw)
Sent from my iPad
next reply other threads:[~2022-07-19 2:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 2:11 Robin Naccari [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-17 19:39 [PATCH v2 0/4] Atomic addfd send and reply Sargun Dhillon
2021-05-17 19:39 ` [PATCH v2 3/4] seccomp: Support atomic "addfd + send reply" Sargun Dhillon
2021-05-21 15:45 ` Christian Brauner
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=197A77C8-41B4-43E9-9779-CA68F39FD92E@icloud.com \
--to=robianna1973@icloud.com \
--cc=christian.brauner@ubuntu.com \
--cc=containers@lists.linux.dev \
--cc=gscrivan@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mauricio@kinvolk.io \
--cc=mic@linux.microsoft.com \
--cc=rodrigo@kinvolk.io \
--cc=tycho@tycho.pizza \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).