From: Christian Brauner <christian.brauner@ubuntu.com>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: Kees Cook <keescook@chromium.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
linux-api@vger.kernel.org, Jann Horn <jannh@google.com>,
Arnd Bergmann <arnd@arndb.de>, Helge Deller <deller@gmx.de>
Subject: Re: [RFC][PATCH] sysctl: Remove the sysctl system call
Date: Thu, 3 Oct 2019 23:08:14 +0200 [thread overview]
Message-ID: <20191003210814.gh7rbbv6bpxlhz3w@wittgenstein> (raw)
In-Reply-To: <87y2y271ws.fsf@mid.deneb.enyo.de>
On Thu, Oct 03, 2019 at 08:56:19AM +0200, Florian Weimer wrote:
> Is anyone else getting a very incomplete set of messages in this
> thread?
>
> These changes likely matter to glibc, and I've yet to see the actual
> patch. Would someone please forward it to me?
>
> The original message didn't make it into the lore.kernel.org archives
> (the cross-post to linux-kernel should have taken care of that).
Yeah, I didn't get it either and the repost too weirdly enough.
Christian
next prev parent reply other threads:[~2019-10-03 21:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8736gcjosv.fsf@x220.int.ebiederm.org>
2019-10-01 18:46 ` [RFC][PATCH] sysctl: Remove the sysctl system call Kees Cook
2019-10-01 22:53 ` Eric W. Biederman
2019-10-02 0:40 ` Jann Horn
2019-10-02 7:31 ` Arnd Bergmann
2019-10-02 14:41 ` Eric W. Biederman
2019-10-02 14:49 ` Eric W. Biederman
2019-10-02 18:52 ` Helge Deller
2019-10-03 6:56 ` Florian Weimer
[not found] ` <87tv8pftjj.fsf_-_@x220.int.ebiederm.org>
2019-10-03 21:05 ` [REPOST][RFC][PATCH] " Kees Cook
2019-10-08 10:30 ` Michael Kerrisk (man-pages)
2019-10-03 21:08 ` Christian Brauner [this message]
2019-10-04 7:31 ` vger mail woes? (was: Re: [RFC][PATCH] sysctl: Remove the sysctl system call) Florian Weimer
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=20191003210814.gh7rbbv6bpxlhz3w@wittgenstein \
--to=christian.brauner@ubuntu.com \
--cc=arnd@arndb.de \
--cc=deller@gmx.de \
--cc=ebiederm@xmission.com \
--cc=fw@deneb.enyo.de \
--cc=jannh@google.com \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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