linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mingye Wang <arthur200126@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: [PATCH] random.{4,7}, getrandom.2: Adapt to Linux 5.6 changes
Date: Fri, 2 Jun 2023 19:35:16 +0800	[thread overview]
Message-ID: <CAD66C+aPZxQ+FQaFUgDAZoD_FSamWLTUiBjD8ZC3kCHn2HdVfw@mail.gmail.com> (raw)
In-Reply-To: <c4ec42cd-c72d-76e2-0078-f8b68f525152@gmail.com>

Hi Alex,

On Thu, Jun 1, 2023 at 6:20 AM Alejandro Colomar <alx.manpages@gmail.com> wrote:
> If some changes come from Linux 4.8, I prefer having two separate patches.

Will do.

> Just wondering:  how is this description of /dev/urandom different from
> GRND_INSECURE?

It isn't! I reckon that they added the flag to give device file parity.

> Blank lines are wrong.

Will fix.

Thanks,
Mingye

  reply	other threads:[~2023-06-02 11:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-30 16:42 [Bug 214885] New: random.{4,7} [man-pages 5.13] do not reflect changes to /dev/random semantics since kernel 5.6 bugzilla-daemon
2021-10-30 17:01 ` [Bug 214885] " bugzilla-daemon
2023-05-25 11:34 ` bugzilla-daemon
2023-05-25 12:36 ` bugzilla-daemon
2023-05-29  8:50   ` [PATCH] random.{4,7}, getrandom.2: Adapt to Linux 5.6 changes Mingye Wang
2023-05-31 22:20     ` Alejandro Colomar
2023-06-02 11:35       ` Mingye Wang [this message]
2023-06-05  3:13         ` Mingye Wang
2023-07-08 19:06           ` Alejandro Colomar
2024-03-25 12:44 ` [Bug 214885] random.{4,7} [man-pages 5.13] do not reflect changes to /dev/random semantics since kernel 5.6 bugzilla-daemon
2024-03-25 13:26 ` bugzilla-daemon

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=CAD66C+aPZxQ+FQaFUgDAZoD_FSamWLTUiBjD8ZC3kCHn2HdVfw@mail.gmail.com \
    --to=arthur200126@gmail.com \
    --cc=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    /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).