linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
	Vitaly Andrianov <vitalya@ti.com>, Tero Kristo <t-kristo@ti.com>,
	Murali Karicheri <m-karicheri2@ti.com>,
	Matt Mackall <mpm@selenic.com>
Subject: Re: [PATCH] hw_random: move TI Keystone driver into the config menu structure
Date: Thu, 12 Mar 2020 23:39:20 +1100	[thread overview]
Message-ID: <20200312123920.GE28885@gondor.apana.org.au> (raw)
In-Reply-To: <06417e19-57fe-c090-c493-d4c481dfee00@infradead.org>

On Wed, Mar 04, 2020 at 10:21:48PM -0800, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
> 
> Move the TI Keystone hardware random number generator into the
> same menu as all of the other hardware random number generators.
> 
> This makes the driver config be listed in the correct place in
> the kconfig tools.
> 
> Fixes: eb428ee0e3ca ("hwrng: ks-sa - add hw_random driver")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Vitaly Andrianov <vitalya@ti.com>
> Cc: Tero Kristo <t-kristo@ti.com>
> Cc: Murali Karicheri <m-karicheri2@ti.com>
> Cc: Herbert Xu <herbert@gondor.apana.org.au>
> Cc: Matt Mackall <mpm@selenic.com>
> Cc: linux-crypto@vger.kernel.org
> ---
>  drivers/char/hw_random/Kconfig |   14 +++++++-------
>  1 file changed, 7 insertions(+), 7 deletions(-)

Patch applied.  Thanks.
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

      reply	other threads:[~2020-03-12 12:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-05  6:21 [PATCH] hw_random: move TI Keystone driver into the config menu structure Randy Dunlap
2020-03-12 12:39 ` Herbert Xu [this message]

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=20200312123920.GE28885@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m-karicheri2@ti.com \
    --cc=mpm@selenic.com \
    --cc=rdunlap@infradead.org \
    --cc=t-kristo@ti.com \
    --cc=vitalya@ti.com \
    /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;
as well as URLs for NNTP newsgroup(s).