From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: kuba@kernel.org, tytso@mit.edu, elver@google.com,
yury.norov@gmail.com, linux@dominikbrodowski.net,
gregkh@linuxfoundation.org, pmladek@suse.com,
keescook@chromium.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] random: Include <linux/once.h> in the right header
Date: Sat, 3 Dec 2022 02:03:33 +0100 [thread overview]
Message-ID: <Y4qgZUfcnQvL3hYm@zx2c4.com> (raw)
In-Reply-To: <212adb212cb0234a7d395daf31b2578b9409d492.1670015476.git.christophe.jaillet@wanadoo.fr>
Hi Christophe,
On Fri, Dec 02, 2022 at 10:13:36PM +0100, Christophe JAILLET wrote:
> <linux/prandom.h> uses DO_ONCE(). So it should include <linux/once.h>
> directly.
>
> On the contrary, <linux/random.h> doesn't use functionalities from
> <linux/once.h>, so it should be removed.
>
> All this is true since commit c0842fbc1b18 ("random32: move the
> pseudo-random 32-bit definitions to prandom.h")
>
> Move the #include <linux/once.h> in the right file.
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Thanks, applied for now as:
https://git.kernel.org/pub/scm/linux/kernel/git/crng/random.git/commit/?id=1ea746beac98ad11132b0a9a11978d5cf0a055ef
> ---
> Let see if build-bots agree with me!
Indeed. I've got a few builds of my own going, and so far so good, but
we'll learn soon enough if something goes wrong.
Jason
prev parent reply other threads:[~2022-12-03 1:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 21:13 [PATCH] random: Include <linux/once.h> in the right header Christophe JAILLET
2022-12-02 21:17 ` Kees Cook
2022-12-03 1:03 ` Jason A. Donenfeld [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=Y4qgZUfcnQvL3hYm@zx2c4.com \
--to=jason@zx2c4.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=elver@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=pmladek@suse.com \
--cc=tytso@mit.edu \
--cc=yury.norov@gmail.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