From: Dave Jones <davej@codemonkey.org.uk>
To: tyson.w.smith@gmail.com
Cc: trinity@vger.kernel.org, tysmith@motorola.com
Subject: Re: [PATCH 2/7] remove randbits()
Date: Tue, 17 Mar 2015 10:30:46 -0400 [thread overview]
Message-ID: <20150317143046.GB17556@codemonkey.org.uk> (raw)
In-Reply-To: <1426537541-54831-1-git-send-email-tyson.w.smith@gmail.com>
On Mon, Mar 16, 2015 at 01:25:41PM -0700, tyson.w.smith@gmail.com wrote:
> From: Tyson Smith <tyson.w.smith@gmail.com>
>
> randbits() acts very much like rand() & rand() and does not
> provide much value in this context. This function would likely
> be more useful in a random bit mask scenario.
Where are we doing rand() & rand() ?
The changelog implies we're doing this elsewhere, and that this
is duplication, but I'm not seeing it.
Dave
prev parent reply other threads:[~2015-03-17 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 20:25 [PATCH 2/7] remove randbits() tyson.w.smith
2015-03-17 14:30 ` Dave Jones [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=20150317143046.GB17556@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=trinity@vger.kernel.org \
--cc=tysmith@motorola.com \
--cc=tyson.w.smith@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;
as well as URLs for NNTP newsgroup(s).