From: George Spelvin <lkml@sdf.org>
To: daniel@iogearbox.net, hannes@stressinduktion.org
Cc: lkml@sdf.org, netdev@vger.kernel.org
Subject: Re: Revising prandom_32 generator
Date: Tue, 26 Mar 2019 11:17:29 GMT [thread overview]
Message-ID: <201903261117.x2QBHTnl002697@sdf.org> (raw)
In-Reply-To: <201903261110.x2QBAFmp001613@sdf.org>
Apologies... I severely mangled the headers in the previous
message, feeding "Daniel Borkmann <daniel@iogearbox.net>" to a
parser which split on whitespace and thought that was three separate
recipients. :-(
To limit the damage, please either reply to *this* message or trim the
headers manually. Sorry about that.
next prev parent reply other threads:[~2019-03-26 11:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 11:10 Revising prandom_32 generator George Spelvin
2019-03-26 11:17 ` George Spelvin [this message]
2019-03-26 18:03 ` Hannes Frederic Sowa
2019-03-26 19:07 ` George Spelvin
2019-03-26 19:23 ` Stephen Hemminger
2019-03-27 18:32 ` Hannes Frederic Sowa
2019-03-27 21:43 ` George Spelvin
2019-03-26 14:58 ` Stephen Hemminger
2019-03-26 16:24 ` George Spelvin
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=201903261117.x2QBHTnl002697@sdf.org \
--to=lkml@sdf.org \
--cc=daniel@iogearbox.net \
--cc=hannes@stressinduktion.org \
--cc=netdev@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