From: Eric Biggers <ebiggers@kernel.org>
To: stable@vger.kernel.org
Cc: stable-commits@vger.kernel.org,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
Ard Biesheuvel <ardb@kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>
Subject: Re: Patch "crypto: powerpc/poly1305 - add depends on BROKEN for now" has been added to the 6.12-stable tree
Date: Mon, 7 Jul 2025 21:37:40 +0000 [thread overview]
Message-ID: <20250707213740.GB3178810@google.com> (raw)
In-Reply-To: <20250707172944.GA3116681@google.com>
On Mon, Jul 07, 2025 at 05:29:47PM +0000, Eric Biggers wrote:
> On Mon, Jul 07, 2025 at 12:34:45AM -0400, Sasha Levin wrote:
> > This is a note to let you know that I've just added the patch titled
> >
> > crypto: powerpc/poly1305 - add depends on BROKEN for now
> >
> > to the 6.12-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>
> You forgot to Cc the relevant mailing lists.
>
> > diff --git a/arch/powerpc/lib/crypto/Kconfig b/arch/powerpc/lib/crypto/Kconfig
> > new file mode 100644
> > index 0000000000000..3f9e1bbd9905b
> > --- /dev/null
> > +++ b/arch/powerpc/lib/crypto/Kconfig
> > @@ -0,0 +1,22 @@
> > +# SPDX-License-Identifier: GPL-2.0-only
> > +
> > +config CRYPTO_CHACHA20_P10
> > + tristate
> > + depends on PPC64 && CPU_LITTLE_ENDIAN && VSX
> > + default CRYPTO_LIB_CHACHA
> > + select CRYPTO_LIB_CHACHA_GENERIC
> > + select CRYPTO_ARCH_HAVE_LIB_CHACHA
> > +
> > +config CRYPTO_POLY1305_P10
> > + tristate
> > + depends on PPC64 && CPU_LITTLE_ENDIAN && VSX
> > + depends on BROKEN # Needs to be fixed to work in softirq context
> > + default CRYPTO_LIB_POLY1305
> > + select CRYPTO_ARCH_HAVE_LIB_POLY1305
> > + select CRYPTO_LIB_POLY1305_GENERIC
> > +
> > +config CRYPTO_SHA256_PPC_SPE
> > + tristate
> > + depends on SPE
> > + default CRYPTO_LIB_SHA256
> > + select CRYPTO_ARCH_HAVE_LIB_SHA256
>
> Really?
I see this was already backported correctly for 6.15, so please just
cherry-pick it from there.
- Eric
next prev parent reply other threads:[~2025-07-07 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250707043445.484247-1-sashal@kernel.org>
2025-07-07 17:29 ` Patch "crypto: powerpc/poly1305 - add depends on BROKEN for now" has been added to the 6.12-stable tree Eric Biggers
2025-07-07 21:37 ` Eric Biggers [this message]
2025-07-08 15:33 ` Greg KH
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=20250707213740.GB3178810@google.com \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@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