From: Eric Biggers <ebiggers@kernel.org>
To: Richard Weinberger <richard@sigma-star.at>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Richard Weinberger <richard@nod.at>,
upstream@sigma-star.at, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org, demiobenour@gmail.com,
davem@davemloft.net, upstream+linux@sigma-star.at
Subject: Re: [PATCH] crypto: af_alg: Allow cbc(paes)
Date: Thu, 30 Jul 2026 09:55:53 -0700 [thread overview]
Message-ID: <20260730165553.GA3139@sol> (raw)
In-Reply-To: <4313653.jTJXf6HLCa@nailgun>
On Thu, Jul 30, 2026 at 09:56:41AM +0200, Richard Weinberger wrote:
> On Donnerstag, 30. Juli 2026 09:54 Herbert Xu wrote:
> > On Thu, Jul 30, 2026 at 09:52:44AM +0200, Richard Weinberger wrote:
> > >
> > > Eric asked me to wait a bit before I send a patch for next:
> > > https://lore.kernel.org/linux-crypto/20260727172004.GA877700@google.com/
> >
> > Well if I'm going to apply your patch I need to know what you want
> > this to do in next.
> >
> > Are you happy to leave it as denied for next?
>
> No.
> I'll happily send a patch for next just.
>
> I just did what Eric told me and waited.
>
> Thanks,
> //richard
I assumed it would be:
1. patch crypto/master (for 7.2)
2. merge crypto/master into cryptodev/master
3. patch cryptodev/master to add an allowlist entry (for the
algorithm name, not the mask which was already done by (1))
But Herbert maintains this code, so if he wants them to merge in another
order you'll need to do that.
I'm not sure why my email above is linked to. That email was about the
implementation, not where/when the patches should go.
- Eric
prev parent reply other threads:[~2026-07-30 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-26 19:27 [PATCH] crypto: af_alg: Allow cbc(paes) Richard Weinberger
2026-07-27 18:25 ` Eric Biggers
2026-07-30 7:37 ` Herbert Xu
2026-07-30 7:39 ` Richard Weinberger
2026-07-30 7:50 ` Herbert Xu
2026-07-30 7:52 ` Richard Weinberger
2026-07-30 7:54 ` Herbert Xu
2026-07-30 7:56 ` Richard Weinberger
2026-07-30 16:55 ` 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=20260730165553.GA3139@sol \
--to=ebiggers@kernel.org \
--cc=davem@davemloft.net \
--cc=demiobenour@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
--cc=richard@sigma-star.at \
--cc=upstream+linux@sigma-star.at \
--cc=upstream@sigma-star.at \
/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