[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHmME9ogAW0o2PReNtsD+fFgwp28q2kP7WADtbd8kA7GsnKBpg@mail.gmail.com>
Date: Tue, 18 Jan 2022 12:43:09 +0100
From: "Jason A. Donenfeld" <Jason@...c4.com>
To: Herbert Xu <herbert@...dor.apana.org.au>
Cc: geert@...ux-m68k.org, linux-crypto@...r.kernel.org,
netdev@...r.kernel.org, wireguard@...ts.zx2c4.com,
linux-kernel@...r.kernel.org, bpf@...r.kernel.org, tytso@....edu,
gregkh@...uxfoundation.org, jeanphilippe.aumasson@...il.com,
ardb@...nel.org
Subject: Re: [PATCH crypto v3 0/2] reduce code size from blake2s on m68k and
other small platforms
On 1/18/22, Herbert Xu <herbert@...dor.apana.org.au> wrote:
> As the patches that triggered this weren't part of the crypto
> tree, this will have to go through the random tree if you want
> them for 5.17.
Sure, will do.
Powered by blists - more mailing lists