From: Peter Zijlstra <peterz@infradead.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
"Greg KH" <gregkh@linuxfoundation.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Kees Cook" <keescook@chromium.org>,
"Sedat Dilek" <sedat.dilek@gmail.com>,
"Nick Clifton" <nickc@redhat.com>,
"Fāng-ruì Sòng" <maskray@google.com>,
"Segher Boessenkool" <segher@kernel.crashing.org>,
"Rasmus Villemoes" <linux@rasmusvillemoes.dk>,
clang-built-linux <clang-built-linux@googlegroups.com>,
LKML <linux-kernel@vger.kernel.org>,
postmaster@vger.kernel.org, "David Miller" <davem@davemloft.net>
Subject: Re: linux tooling mailing list
Date: Wed, 30 Sep 2020 19:37:19 +0200 [thread overview]
Message-ID: <20200930173719.GE2628@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CAKwvOdmFm9-FPrqt42NsusWRbDzNx6NF1GeSJhz_9kaAGV8eOA@mail.gmail.com>
On Wed, Sep 30, 2020 at 10:25:40AM -0700, Nick Desaulniers wrote:
> Does anyone know who's behind postmaster@vger.kernel.org? Maybe I can
> email them directly if perhaps they don't check this email often?
> (Benefit of the doubt)
davem iirc.
next prev parent reply other threads:[~2020-09-30 17:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKwvOdkHzbPjw71n+RVXuM6Wt6PNO6fiy+14QTzthF7MCkewwg@mail.gmail.com>
[not found] ` <CA+icZUWvEzUhCjkMYAK22pkjshKmfE4a2y_W0sPPuqRtzXOtNw@mail.gmail.com>
[not found] ` <CAFP8O3LQSS4BufLEPQKOk62T0d8HoZq0kQAU8+K4d4gpY4CPag@mail.gmail.com>
[not found] ` <CA+icZUU44tbsmGfTc-2OO42V42Z02dRSs7AZCJBnXL65vJDz-Q@mail.gmail.com>
[not found] ` <664e5923-d65e-0a3a-1320-8b6635146676@redhat.com>
2020-09-15 20:49 ` Nick Desaulniers
2020-09-30 17:25 ` Nick Desaulniers
2020-09-30 17:37 ` Peter Zijlstra [this message]
2020-09-30 19:29 ` Nick Desaulniers
2020-09-30 22:26 ` David Miller
2020-10-02 11:33 ` Nick Clifton
2020-10-02 12:01 ` Sedat Dilek
2020-10-02 17:22 ` Segher Boessenkool
2020-10-02 17:37 ` Randy Dunlap
2020-10-05 17:50 ` Nick Desaulniers
2020-10-05 17:57 ` Sedat Dilek
2020-10-05 23:59 ` David Miller
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=20200930173719.GE2628@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=clang-built-linux@googlegroups.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=maskray@google.com \
--cc=ndesaulniers@google.com \
--cc=nickc@redhat.com \
--cc=postmaster@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=segher@kernel.crashing.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®