From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Dominik Brodowski <linux@dominikbrodowski.net>,
"Theodore Ts'o" <tytso@mit.edu>
Subject: Re: [PATCH v2 09/10] random: group sysctl functions
Date: Mon, 21 Feb 2022 16:39:05 +0100 [thread overview]
Message-ID: <CAHmME9r0H7BzU2B+X=twh7JWAo7EaaRv6NRVK3sEbDh2v=VLYA@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9o5FhAWYS7bfnXzNzLBtCadAYWXHjmE2tZNMG3C64NeKw@mail.gmail.com>
On Mon, Feb 21, 2022 at 4:27 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
> On Mon, Feb 21, 2022 at 6:21 AM Eric Biggers <ebiggers@kernel.org> wrote:
> > This is a nice explanation, but shouldn't
> > Documentation/admin-guide/sysctl/kernel.rst be updated instead, and this comment
> > point to there?
>
> I'll update kernel.rst for this and for the other thing in a separate
> commit to make merge conflicts less annoying.
Actually, it's not that bad. I'll update kernel.rst in the commits
where the behavior needs updating, but I'm fine with the slightly
different wording there for the most part.
next prev parent reply other threads:[~2022-02-21 15:39 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 12:23 [PATCH v2 00/10] random: re-group and re-document functions Jason A. Donenfeld
2022-02-12 12:23 ` [PATCH v2 01/10] random: introduce drain_entropy() helper to declutter crng_reseed() Jason A. Donenfeld
2022-02-21 4:34 ` Eric Biggers
2022-02-21 14:49 ` Jason A. Donenfeld
2022-02-21 14:49 ` [PATCH v3] " Jason A. Donenfeld
2022-02-21 19:19 ` Eric Biggers
2022-02-12 12:23 ` [PATCH v2 02/10] random: remove useless header comment Jason A. Donenfeld
2022-02-21 4:34 ` Eric Biggers
2022-02-12 12:23 ` [PATCH v2 03/10] random: remove whitespace and reorder includes Jason A. Donenfeld
2022-02-21 4:35 ` Eric Biggers
2022-02-12 12:23 ` [PATCH v2 04/10] random: group initialization wait functions Jason A. Donenfeld
2022-02-13 6:54 ` Dominik Brodowski
2022-02-13 13:11 ` Jason A. Donenfeld
2022-02-21 4:49 ` Eric Biggers
2022-02-21 15:10 ` Jason A. Donenfeld
2022-02-21 15:14 ` [PATCH v3] " Jason A. Donenfeld
2022-02-21 19:20 ` Eric Biggers
2022-02-12 12:23 ` [PATCH v2 05/10] random: group crng functions Jason A. Donenfeld
2022-02-13 6:54 ` Dominik Brodowski
2022-02-13 13:14 ` Jason A. Donenfeld
2022-02-21 5:00 ` Eric Biggers
2022-02-12 12:23 ` [PATCH v2 06/10] random: group entropy extraction functions Jason A. Donenfeld
2022-02-21 5:05 ` Eric Biggers
2022-02-12 12:23 ` [PATCH v2 07/10] random: group entropy collection functions Jason A. Donenfeld
2022-02-13 6:54 ` Dominik Brodowski
2022-02-13 13:16 ` Jason A. Donenfeld
2022-02-21 5:13 ` Eric Biggers
2022-02-21 15:17 ` Jason A. Donenfeld
2022-02-21 15:18 ` [PATCH v3] " Jason A. Donenfeld
2022-02-21 19:23 ` Eric Biggers
2022-02-12 12:23 ` [PATCH v2 08/10] random: group userspace read/write functions Jason A. Donenfeld
2022-02-21 5:16 ` Eric Biggers
2022-02-12 12:23 ` [PATCH v2 09/10] random: group sysctl functions Jason A. Donenfeld
2022-02-21 5:21 ` Eric Biggers
2022-02-21 15:27 ` Jason A. Donenfeld
2022-02-21 15:39 ` Jason A. Donenfeld [this message]
2022-02-12 12:23 ` [PATCH v2 10/10] random: rewrite header introductory comment Jason A. Donenfeld
2022-02-21 5:26 ` Eric Biggers
2022-02-13 6:55 ` [PATCH v2 00/10] random: re-group and re-document functions Dominik Brodowski
2022-02-13 13:07 ` 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='CAHmME9r0H7BzU2B+X=twh7JWAo7EaaRv6NRVK3sEbDh2v=VLYA@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=ebiggers@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--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).