From: Conor Dooley <conor.dooley@microchip.com>
To: Peter Lafreniere <peter@n8pjl.ca>
Cc: Ard Biesheuvel <ardb@kernel.org>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] crypto: x86 - exit fpu context earlier in ECB/CBC macros
Date: Mon, 16 Jan 2023 15:32:23 +0000 [thread overview]
Message-ID: <Y8VuB7kmn9dQ8/en@wendy> (raw)
In-Reply-To: <T7YG602WaDuPk4rYB6-BwCn0pdxSTJxyOR7-vs59gUu1sXMFtkbjCUd1DZ9xuFy9724II9A1qQWf0hKsLJ04qawtcrfO90FA5eYn5hyLzvw=@n8pjl.ca>
[-- Attachment #1: Type: text/plain, Size: 745 bytes --]
On Mon, Jan 16, 2023 at 03:20:59PM +0000, Peter Lafreniere wrote:
> > Please don't send encrypted emails to the mailing list. Plaintext
> > only, with the patch in the message body (not as an attachment).
> > Please use git send-email if you have trouble configuring your email
> > client.
> My apologies. I was having difficulties configuring git send-email,
> but now I believe that I have the issues resolved. Future patches will
> be properly formatted.
It landed okay on lore:
https://lore.kernel.org/linux-crypto/IBooTlGWpNE7pOelt0gm21bxW7wBILNYJ1HaoPbbfdEEMwz0Pp92vpd_OUlhNFNAitFThTi27P6q6NvcYMKm-y7tjwiF9YbImWjhgC3UDMk=@n8pjl.ca/#t
I've seen enough of these now to know where this is going, I'd bet that
you're a protonmail user...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-01-16 15:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 14:59 Peter Lafreniere
2023-01-16 15:09 ` Ard Biesheuvel
2023-01-16 15:20 ` Peter Lafreniere
2023-01-16 15:32 ` Conor Dooley [this message]
2023-01-16 15:40 ` Peter Lafreniere
2023-01-16 16:27 ` Conor.Dooley
2023-01-16 16:33 ` Ard Biesheuvel
2023-01-27 10:53 ` Herbert Xu
2023-01-27 11:09 ` Ard Biesheuvel
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=Y8VuB7kmn9dQ8/en@wendy \
--to=conor.dooley@microchip.com \
--cc=ardb@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@n8pjl.ca \
--cc=x86@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
all inboxes | Powered by JetHome®