From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2FD06C54EBE for ; Mon, 16 Jan 2023 15:41:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230411AbjAPPlB (ORCPT ); Mon, 16 Jan 2023 10:41:01 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57838 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230497AbjAPPkr (ORCPT ); Mon, 16 Jan 2023 10:40:47 -0500 Received: from mail-40136.proton.ch (mail-40136.proton.ch [185.70.40.136]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1AF3EA262; Mon, 16 Jan 2023 07:40:44 -0800 (PST) Date: Mon, 16 Jan 2023 15:40:28 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=n8pjl.ca; s=protonmail; t=1673883642; x=1674142842; bh=hMNV5Q9auz+Z6acJq71QxOGvPxX4ImxbwQzC4E0AbgQ=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=sscnZ5efTfSAVNeNKWUeE1is2n/3P5oD3G+PoCtR1sDcIqV48NZNheA+tvWANEMzn QQnu9O9Csq22VlTBKOhSjUVMn3oFkfYF4+3yo2GEYPzGvKLW+of5bNM7q4TEM5wNYa zIfCwpFT2qBQ816PBBbqqP0Gk5uuxDMQghwecURaxXGRIGp2CE5F1pwG+lmSpTfjKR yH2V/GVXXbEMbdBI3EvUyxV73nQmMEkkEY73iFLepyUHIRV8CZWDW4LbGAICAn3KdA eHeaRXPs+8h+ysLb0bGPnic2loSkMtWWyndqJoUaqN+jAUEO1qmw0AhAV4nVwLyLvn qkJFdBF7xYqww== To: Conor Dooley From: Peter Lafreniere Cc: Ard Biesheuvel , "linux-crypto@vger.kernel.org" , "x86@kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH] crypto: x86 - exit fpu context earlier in ECB/CBC macros Message-ID: In-Reply-To: References: Feedback-ID: 53133685:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org > > 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. >=20 >=20 > It landed okay on lore: > https://lore.kernel.org/linux-crypto/IBooTlGWpNE7pOelt0gm21bxW7wBILNYJ1Ha= oPbbfdEEMwz0Pp92vpd_OUlhNFNAitFThTi27P6q6NvcYMKm-y7tjwiF9YbImWjhgC3UDMk=3D@= n8pjl.ca/#t Yup, that's why I'm not resending it. >=20 > 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=20 good now. Again, sorry for the issues, Peter Lafreniere