From: Ard Biesheuvel <ardb@kernel.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: "Justin M. Forbes" <jforbes@fedoraproject.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Justin Forbes <jmforbes@linuxtx.org>
Subject: Re: [PATCH v2] lib/crypto: add prompts back to crypto libraries
Date: Wed, 12 Jan 2022 15:08:39 +0100 [thread overview]
Message-ID: <CAMj1kXGzzHefRu1wcgDsYpybSDrUK__FXE-Mjm2r1fg2xiz6Jg@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9oKEawBAGSN_tdpBDe2_vRUE8Gh+GMXn+d94A6te4FJPQ@mail.gmail.com>
On Wed, 12 Jan 2022 at 15:08, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
> On Wed, Jan 12, 2022 at 3:06 PM Ard Biesheuvel <ardb@kernel.org> wrote:
> >
> > On Wed, 12 Jan 2022 at 15:05, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> > >
> > > This commit also needs this snippet:
> > >
> >
> > Why?
>
> So that the menu of crypto library options is inside of the library
> menu. Otherwise this will appear inside of the _root_ menu, which
> isn't what we want.
Why not? I think that's fine.
next prev parent reply other threads:[~2022-01-12 14:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 14:01 [PATCH v2] lib/crypto: add prompts back to crypto libraries Justin M. Forbes
2022-01-12 14:04 ` Jason A. Donenfeld
2022-01-12 14:06 ` Ard Biesheuvel
2022-01-12 14:07 ` Jason A. Donenfeld
2022-01-12 14:08 ` Ard Biesheuvel [this message]
2022-01-12 14:11 ` Jason A. Donenfeld
2022-01-12 14:13 ` Ard Biesheuvel
2022-01-12 14:14 ` Jason A. Donenfeld
2022-01-12 14:19 ` Justin Forbes
2022-01-12 14:20 ` Jason A. Donenfeld
2022-01-12 14:41 ` Ard Biesheuvel
2022-01-12 14:44 ` Jason A. Donenfeld
2022-01-12 14:49 ` Ard Biesheuvel
2022-01-12 14:53 ` Jason A. Donenfeld
2022-01-12 14:57 ` [PATCH v3] " Jason A. Donenfeld
2022-01-16 16:58 ` [PATCH v4] " Jason A. Donenfeld
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=CAMj1kXGzzHefRu1wcgDsYpybSDrUK__FXE-Mjm2r1fg2xiz6Jg@mail.gmail.com \
--to=ardb@kernel.org \
--cc=Jason@zx2c4.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=jforbes@fedoraproject.org \
--cc=jmforbes@linuxtx.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.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.