From: Paul Walmsley <paul.walmsley@sifive.com>
To: Kees Cook <keescook@chromium.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
David Abdurachmanov <david.abdurachmanov@sifive.com>,
Andy Lutomirski <luto@kernel.org>, Borislav Petkov <bp@suse.de>,
bpf@vger.kernel.org,
Christian Brauner <christian.brauner@ubuntu.com>,
Daniel Borkmann <daniel@iogearbox.net>,
kernel test robot <rong.a.chen@intel.com>,
linux-arm-kernel@lists.infradead.org,
linux-kselftest@vger.kernel.org, linux-parisc@vger.kernel.org,
linux-s390@vger.kernel.org, linux-um@lists.infradead.org,
Martin KaFai Lau <kafai@fb.com>,
netdev@vger.kernel.org, Oleg Nesterov <oleg@redhat.com>,
Shuah Khan <shuah@kernel.org>, Song Liu <songliubraving@fb.com>,
Thomas Gleixner <tglx@linutronix.de>,
Tycho Andersen <tycho@tycho.ws>,
Tyler Hicks <tyhicks@canonical.com>,
Will Drewry <wad@chromium.org>,
x86@kernel.org, Yonghong Song <yhs@fb.com>
Subject: Re: [GIT PULL] seccomp updates for v5.5-rc1
Date: Tue, 26 Nov 2019 16:59:11 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1911261656110.23039@viisi.sifive.com> (raw)
In-Reply-To: <201911260818.9C5DC1E@keescook>
On Tue, 26 Nov 2019, Kees Cook wrote:
> Most notably, the secure_computing() prototype has changed (to remove an
> unused argument), but this has happened at the same time as riscv adding
> seccomp support, so the cleanest merge order would be to merge riscv
> first, then seccomp with the following patch for riscv to handle the
> change from "seccomp: simplify secure_computing()":
The RISC-V pull request that contains the seccomp change has been sent.
It's here:
https://lore.kernel.org/linux-riscv/alpine.DEB.2.21.9999.1911261311520.23039@viisi.sifive.com/T/#u
- Paul
next prev parent reply other threads:[~2019-11-27 0:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 16:25 [GIT PULL] seccomp updates for v5.5-rc1 Kees Cook
2019-11-27 0:59 ` Paul Walmsley [this message]
2019-12-01 1:40 ` 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=alpine.DEB.2.21.9999.1911261656110.23039@viisi.sifive.com \
--to=paul.walmsley@sifive.com \
--cc=ast@kernel.org \
--cc=bp@suse.de \
--cc=bpf@vger.kernel.org \
--cc=christian.brauner@ubuntu.com \
--cc=daniel@iogearbox.net \
--cc=david.abdurachmanov@sifive.com \
--cc=kafai@fb.com \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=luto@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=rong.a.chen@intel.com \
--cc=shuah@kernel.org \
--cc=songliubraving@fb.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=tycho@tycho.ws \
--cc=tyhicks@canonical.com \
--cc=wad@chromium.org \
--cc=x86@kernel.org \
--cc=yhs@fb.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).