From: Joe Perches <joe@perches.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>, linux-kernel@vger.kernel.org
Cc: Theodore Ts'o <tytso@mit.edu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] MAINTAINERS: co-maintain random.c
Date: Tue, 30 Nov 2021 17:01:27 -0800 [thread overview]
Message-ID: <1c2862682ff04463c7ca1f58f1c46aec4d6af03d.camel@perches.com> (raw)
In-Reply-To: <20211130184315.258150-1-Jason@zx2c4.com>
On Tue, 2021-11-30 at 13:43 -0500, Jason A. Donenfeld wrote:
> random.c is a bit understaffed, and folks want more prompt reviews. I've
> got the crypto background and the interest to do these reviews, and have
> authored parts of the file already.
[]
> diff --git a/MAINTAINERS b/MAINTAINERS
[]
> @@ -15979,6 +15979,7 @@ F: arch/mips/generic/board-ranchu.c
>
> RANDOM NUMBER DRIVER
> M: "Theodore Ts'o" <tytso@mit.edu>
> +M: Jason A. Donenfeld <Jason@zx2c4.com>
Thank you.
I suggest you reverse the entry order too as Ted really
hasn't done much to random.c for quite awhile.
It's been over 2 years since Ted even acked a patch.
$ git log --no-merges --format=email drivers/char/random.c | \
grep -Pi "^Subject:|^Date:|^\w+-by:.*tytso" | \
grep -B2 tytso
Date: Fri, 23 Aug 2019 14:24:51 +0800
Subject: [PATCH] fdt: add support for rng-seed
Reviewed-by: Theodore Ts'o <tytso@mit.edu> # drivers/char/random.c
--
Date: Fri, 22 Jun 2018 09:15:32 +1000
Subject: [PATCH] random: Return nbytes filled from hw RNG
Acked-by: Theodore Ts'o <tytso@mit.edu>
Date: Fri, 22 Jun 2018 09:15:31 +1000
Subject: [PATCH] random: Fix whitespace pre random-bytes work
Acked-by: Theodore Ts'o <tytso@mit.edu>
--
Date: Mon, 9 Apr 2018 15:29:32 +0200
Subject: [PATCH] random: convert to ->poll_mask
Acked-by: Theodore Ts'o <tytso@mit.edu>
--
Date: Fri, 6 Jan 2017 19:32:01 +0100
Subject: [PATCH] random: use chacha20 for get_random_int/long
Suggested-by: Theodore Ts'o <tytso@mit.edu>
--
Date: Fri, 25 Apr 2014 00:36:37 -0700
Subject: [PATCH] random: export add_disk_randomness
Acked-by: "Theodore Ts'o" <tytso@mit.edu>
--
Date: Mon, 11 Nov 2013 12:20:34 +0100
Subject: [PATCH] random32: add prandom_reseed_late() and call when nonblocking
Acked-by: "Theodore Ts'o" <tytso@mit.edu>
--
Date: Mon, 23 Jul 2012 09:47:57 -0700
Subject: [PATCH] random: Add comment to random_initialize()
Suggested-by: Theodore Ts'o <tytso@mit.edu>
--
Date: Thu, 22 Dec 2011 11:36:22 -0800
Subject: [PATCH] random: Use arch_get_random_int instead of cycle counter if
Acked-by: "Theodore Ts'o" <tytso@mit.edu>
--
Date: Tue, 29 May 2007 21:58:10 -0500
Subject: [PATCH] random: fix seeding with zero entropy
Acked-by: "Theodore Ts'o" <tytso@mit.edu>
Date: Tue, 29 May 2007 21:54:27 -0500
Subject: [PATCH] random: fix error in entropy extraction
Acked-by: "Theodore Ts'o" <tytso@mit.edu>
next prev parent reply other threads:[~2021-12-01 1:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 18:43 [PATCH] MAINTAINERS: co-maintain random.c Jason A. Donenfeld
2021-12-01 1:01 ` Joe Perches [this message]
2021-12-01 16:05 ` Jason A. Donenfeld
2021-12-04 15:00 ` Theodore Y. Ts'o
2021-12-04 15:15 ` Jason A. Donenfeld
2021-12-07 15:49 ` Jason A. Donenfeld
2021-12-07 18:01 ` Theodore Y. Ts'o
2021-12-01 20:56 ` Joe Perches
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=1c2862682ff04463c7ca1f58f1c46aec4d6af03d.camel@perches.com \
--to=joe@perches.com \
--cc=Jason@zx2c4.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).