All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
	Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [PATCH crypto v2] crypto: poly1305 - cleanup stray CRYPTO_LIB_POLY1305_RSIZE
Date: Fri, 27 May 2022 23:15:43 +0200	[thread overview]
Message-ID: <CAHmME9oAqBT5bOd94Na-q_tHHNZqVyU7eLk0odei7-KB07VPRA@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=whyH8xx=2LVmOdQDTy9RRqBs_JJz_oMV2+6a2myk8+wow@mail.gmail.com>

Hi Linus,

On Fri, May 27, 2022 at 11:10 PM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> Oh well. I already applied your v1 patch earlier today..
>
>        Linus

Whoops. I sent this to linux-crypto/Herbert assuming that it'd work
with the "2 weeks pass and nobody complains --> queued up" flow of
that list.

I can send you a patch on top of your tree to fix the v1 you applied.
But let's let the kernel test robot chew on my v2 for a day or two.
The crypto/ Kconfig system is incredibly convoluted, and the config
fuzzing the robot does tends to be (unfortunately) helpful.

Jason

  parent reply	other threads:[~2022-05-27 21:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-26  9:35 [PATCH crypto] crypto: poly1305 - cleanup stray CRYPTO_LIB_POLY1305_RSIZE Jason A. Donenfeld
2022-05-27  7:34 ` kernel test robot
2022-05-27 20:19   ` [PATCH crypto v2] " Jason A. Donenfeld
     [not found]     ` <CAHk-=whyH8xx=2LVmOdQDTy9RRqBs_JJz_oMV2+6a2myk8+wow@mail.gmail.com>
2022-05-27 21:15       ` Jason A. Donenfeld [this message]
2022-05-27 22:19         ` Linus Torvalds

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=CAHmME9oAqBT5bOd94Na-q_tHHNZqVyU7eLk0odei7-KB07VPRA@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.