From: "Theodore Ts'o" <tytso@mit.edu>
To: Greg Price <price@mit.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] random: clarify bits/bytes in wakeup thresholds
Date: Sat, 7 Dec 2013 14:20:40 -0500 [thread overview]
Message-ID: <20131207192040.GA13776@thunk.org> (raw)
In-Reply-To: <20131207022803.GZ16018@ringworld.MIT.EDU>
On Fri, Dec 06, 2013 at 09:28:03PM -0500, Greg Price wrote:
> These are a recurring cause of confusion, so rename them to
> hopefully be clearer.
>
> Signed-off-by: Greg Price <price@mit.edu>
Thanks, applied with some merge fix ups to get the patch to apply.
- Ted
prev parent reply other threads:[~2013-12-07 19:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-07 2:27 [3.13 PATCH 0/2] random: bytes vs. bits Greg Price
2013-12-07 2:27 ` [3.13 PATCH 1/2] random: entropy_bytes is actually bits Greg Price
2013-12-07 14:50 ` Theodore Ts'o
2013-12-07 2:28 ` [PATCH 2/2] random: clarify bits/bytes in wakeup thresholds Greg Price
2013-12-07 19:20 ` Theodore Ts'o [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=20131207192040.GA13776@thunk.org \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=price@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