From: Eric Biggers <ebiggers@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
Christoph Hellwig <hch@lst.de>, Kees Cook <kees@kernel.org>
Subject: Re: [PATCH] MAINTAINERS: add entry for crypto library
Date: Thu, 5 Jun 2025 19:27:15 +0000 [thread overview]
Message-ID: <20250605192715.GB945328@google.com> (raw)
In-Reply-To: <CAMj1kXHthZYSrZzUEkMzjO+Jwy2LA4WUCCBosScX3P8FAPn1yQ@mail.gmail.com>
On Thu, Jun 05, 2025 at 09:01:49PM +0200, Ard Biesheuvel wrote:
> On Thu, 5 Jun 2025 at 20:46, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> >
> > On Thu, Jun 5, 2025 at 8:45 PM Linus Torvalds
> > <torvalds@linux-foundation.org> wrote:
> > >
> > > Should I just add you and Jason directly as 'M:' entries for this?
> >
> > Works for me.
>
> Sure.
Listing Ard and Jason as M: is fine with me. I expect that in practice I'll be
applying the patches and doing the pull requests for now, so (as is often the
case with subsystems with multiple M:) in practice it will really be a primary
maintainer and backup maintainer(s). But I'm happy to have Ard and Jason listed
in case one of them needs to step in.
- Eric
prev parent reply other threads:[~2025-06-05 19:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 17:11 [PATCH] MAINTAINERS: add entry for crypto library Eric Biggers
2025-06-05 18:12 ` Jason A. Donenfeld
2025-06-05 18:43 ` Ard Biesheuvel
2025-06-05 18:44 ` Linus Torvalds
2025-06-05 18:45 ` Jason A. Donenfeld
2025-06-05 19:01 ` Ard Biesheuvel
2025-06-05 19:27 ` Eric Biggers [this message]
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=20250605192715.GB945328@google.com \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=davem@davemloft.net \
--cc=hch@lst.de \
--cc=herbert@gondor.apana.org.au \
--cc=kees@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.