From: Christoph Hellwig <hch@infradead.org>
To: Jeff Barnes <jeffbarnes@linux.microsoft.com>
Cc: Joachim Vandersmissen <git@jvdsn.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
Jeff Barnes <jeffbarnes@microsoft.com>
Subject: Re: [PATCH] crypto: aead: add service indicator flag for RFC4106 AES-GCM
Date: Tue, 3 Mar 2026 07:14:28 -0800 [thread overview]
Message-ID: <aab61CI7zajzqu5u@infradead.org> (raw)
In-Reply-To: <145cfedf-7510-44b7-b1b7-6569144e7b21@linux.microsoft.com>
On Mon, Mar 02, 2026 at 04:51:38PM -0500, Jeff Barnes wrote:
> for out-of-tree modules, you're on your own". But that's where the need for
> the service indicator arises. I'm sure that maintaining the out-of-tree
> patch with a service indicator is a royal pain downstream.
And that's a good thing. Maintaining out of tree stuff should be a
royal pain and not impact the upstream kernel in any way.
prev parent reply other threads:[~2026-03-03 15:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 21:04 [PATCH] crypto: aead: add service indicator flag for RFC4106 AES-GCM jeffbarnes
2026-01-30 5:10 ` Herbert Xu
2026-02-17 20:59 ` Jeff Barnes
2026-02-28 8:56 ` Herbert Xu
2026-03-01 20:41 ` Joachim Vandersmissen
2026-03-02 12:26 ` Herbert Xu
2026-03-02 21:34 ` Jeff Barnes
2026-03-02 21:51 ` Jeff Barnes
2026-03-03 3:37 ` Herbert Xu
2026-03-12 14:00 ` Jeff Barnes
2026-03-14 19:37 ` Eric Biggers
2026-03-03 15:14 ` Christoph Hellwig [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=aab61CI7zajzqu5u@infradead.org \
--to=hch@infradead.org \
--cc=davem@davemloft.net \
--cc=git@jvdsn.com \
--cc=herbert@gondor.apana.org.au \
--cc=jeffbarnes@linux.microsoft.com \
--cc=jeffbarnes@microsoft.com \
--cc=linux-crypto@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