From: Sasha Levin <sashal@kernel.org>
To: Greg KH <greg@kroah.com>
Cc: Thomas Backlund <tmb@tmb.nu>, Ard Biesheuvel <ardb@kernel.org>,
"# 3.4.x" <stable@vger.kernel.org>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
Eric Biggers <ebiggers@kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: stable request
Date: Fri, 19 Mar 2021 08:10:33 -0400 [thread overview]
Message-ID: <YFSUuRCbjmpdSOhW@sashalap> (raw)
In-Reply-To: <YFSB3iLXC/DDtN1U@kroah.com>
On Fri, Mar 19, 2021 at 11:50:06AM +0100, Greg KH wrote:
>On Fri, Mar 19, 2021 at 07:35:44AM +0000, Thomas Backlund wrote:
>> Den 18-03-2021 kl. 15:03, skrev Sasha Levin:
>> >
>> > On Tue, Mar 16, 2021 at 01:35:40PM +0100, Ard Biesheuvel wrote:
>> >> On Tue, 16 Mar 2021 at 13:28, Thomas Backlund <tmb@tmb.nu> wrote:
>> >>>
>> >>>
>> >>> Den 16.3.2021 kl. 14:15, skrev Thomas Backlund:
>> >>>>
>> >>>> Den 16.3.2021 kl. 12:17, skrev Ard Biesheuvel:
>> >>>>> On Tue, 16 Mar 2021 at 10:21, Thomas Backlund <tmb@tmb.nu> wrote:
>> >>>>>> Den 16.3.2021 kl. 08:37, skrev Ard Biesheuvel:
>> >>>>>>> Please consider backporting commit
>> >>>>>>>
>> >>>>>>> 86ad60a65f29dd862a11c22bb4b5be28d6c5cef1
>> >>>>>>> crypto: x86/aes-ni-xts - use direct calls to and 4-way stride
>>
>>
>> >
>> > Queued up for 5.10 and 5.11.
>> >
>>
>> I dont see:
>> 86ad60a65f29 ("crypto: x86/aes-ni-xts - use direct calls to and 4-way
>> stride")
>>
>> in 5.11 queue.
>
>Now added by me, Sasha might have forgotten to push his queue...
Thanks Greg, yes - it was sitting locally waiting for my build tests to
finish.
--
Thanks,
Sasha
next prev parent reply other threads:[~2021-03-19 12:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 9:21 stable request Thomas Backlund
2021-03-16 10:17 ` Ard Biesheuvel
2021-03-16 12:15 ` Thomas Backlund
2021-03-16 12:28 ` Thomas Backlund
2021-03-16 12:35 ` Ard Biesheuvel
2021-03-18 13:03 ` Sasha Levin
2021-03-18 14:15 ` Ard Biesheuvel
2021-03-18 16:42 ` Sasha Levin
2021-03-18 17:13 ` Ard Biesheuvel
2021-03-18 17:45 ` Ard Biesheuvel
2021-03-19 7:35 ` Thomas Backlund
2021-03-19 10:50 ` Greg KH
2021-03-19 12:10 ` Sasha Levin [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-03-16 6:37 Ard Biesheuvel
2019-08-23 21:42 [PATCH net-next] net: ipv6: fix listify ip6_rcv_finish in case of forwarding David Miller
2019-10-04 15:17 ` Edward Cree
2019-10-16 15:26 ` Stable request (was " Edward Cree
2019-10-16 17:47 ` Stable request David Miller
2019-10-16 17:47 ` David Miller
2019-10-17 23:50 ` David Miller
2019-10-17 23:50 ` David Miller
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=YFSUuRCbjmpdSOhW@sashalap \
--to=sashal@kernel.org \
--cc=ardb@kernel.org \
--cc=ebiggers@kernel.org \
--cc=greg@kroah.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tmb@tmb.nu \
/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.