linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Mark Brown <broonie@kernel.org>
Cc: tytso@mit.edu, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org,
	Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH] random: Document add_hwgenerator_randomness() with other input functions
Date: Wed, 1 Dec 2021 23:48:58 -0500	[thread overview]
Message-ID: <YahQOjroOQSbB9CR@zx2c4.com> (raw)
In-Reply-To: <20211201174449.1359595-1-broonie@kernel.org>

Hi Mark,

On Wed, Dec 01, 2021 at 05:44:49PM +0000, Mark Brown wrote:
> The section at the top of random.c which documents the input functions
> available does not document add_hwgenerator_randomness() which might lead
> a reader to overlook it. Add a brief note about it.
> 
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
> 
> Ted, I've been sending this for almost two years at this point and
> you've not commented on it - if there's some issue please let me know.

Sorry for the delay. I've queued this up in my random tree now after
incorporating Randy's punctuation suggestion from two of the former
posts:

https://git.kernel.org/zx2c4/random-linux/c/91995de6b6dd91

This will transition through the various trees next time I send a pull.

Regards,
Jason

  reply	other threads:[~2021-12-02  4:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-01 17:44 [PATCH] random: Document add_hwgenerator_randomness() with other input functions Mark Brown
2021-12-02  4:48 ` Jason A. Donenfeld [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-11-15 17:42 Mark Brown
2021-10-15 13:34 Mark Brown
2021-09-21 21:39 Mark Brown
2021-07-12 12:07 Mark Brown
2021-05-11 17:29 Mark Brown
2021-01-13 17:10 Mark Brown
2020-07-01 17:15 Mark Brown
2020-04-24 12:39 Mark Brown
2020-04-24 16:03 ` Randy Dunlap
2020-01-24 13:41 Mark Brown
2020-01-24 20:23 ` Randy Dunlap

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=YahQOjroOQSbB9CR@zx2c4.com \
    --to=jason@zx2c4.com \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=tytso@mit.edu \
    /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).