All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Lafreniere <peter@n8pjl.ca>
To: Conor Dooley <conor.dooley@microchip.com>
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:40:28 +0000	[thread overview]
Message-ID: <dmhKJenSmPJOEexgrs2dFRol14c34HKqMXwGjS-CXVJKZ2hCmR5yN1BG8osscOQvgJaR0wx2AOenX5Zkq34TPpf1BJ9a6zB7ZN79N51wOTI=@n8pjl.ca> (raw)
In-Reply-To: <Y8VuB7kmn9dQ8/en@wendy>

> > 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

Yup, that's why I'm not resending it.

> 
> I've seen enough of these now to know where this is going, I'd bet that
> you're a protonmail user...

You would be quite correct. They do like making your life difficult when
it comes to using smtp.

Anyway, the patch landed fine on lore and patchwork and I've (finally)
configured git-send-email properly, so I think that this should be all 
good now.

Again, sorry for the issues,
Peter Lafreniere

  reply	other threads:[~2023-01-16 15:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-16 14:59 [PATCH] crypto: x86 - exit fpu context earlier in ECB/CBC macros Peter Lafreniere
2023-01-16 15:09 ` Ard Biesheuvel
2023-01-16 15:20   ` Peter Lafreniere
2023-01-16 15:32     ` Conor Dooley
2023-01-16 15:40       ` Peter Lafreniere [this message]
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='dmhKJenSmPJOEexgrs2dFRol14c34HKqMXwGjS-CXVJKZ2hCmR5yN1BG8osscOQvgJaR0wx2AOenX5Zkq34TPpf1BJ9a6zB7ZN79N51wOTI=@n8pjl.ca' \
    --to=peter@n8pjl.ca \
    --cc=ardb@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.