From: Keith Packard <keithp@keithp.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Matt Mackall <mpm@selenic.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwrng: core - allow perfect entropy from hardware devices
Date: Wed, 18 Mar 2015 00:15:49 -0700 [thread overview]
Message-ID: <86oanqbwt6.fsf@hiro.keithp.com> (raw)
In-Reply-To: <20150318051818.GA20194@gondor.apana.org.au>
[-- Attachment #1: Type: text/plain, Size: 270 bytes --]
Herbert Xu <herbert@gondor.apana.org.au> writes:
> Please cc all hwrng patches to linux-crypto@vger.kernel.org so that
> it gets picked up by patchworks. Thanks!
Thanks! I didn't catch that in the MAINTAINERS file. Might be a good
thing to add?
--
-keith
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 810 bytes --]
next prev parent reply other threads:[~2015-03-18 7:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 5:13 [PATCH] hwrng: core - allow perfect entropy from hardware devices Keith Packard
2015-03-18 5:18 ` Herbert Xu
2015-03-18 7:15 ` Keith Packard [this message]
2015-03-18 8:58 ` Herbert Xu
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=86oanqbwt6.fsf@hiro.keithp.com \
--to=keithp@keithp.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.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