From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: backports@vger.kernel.org,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Subject: Re: [PATCH v3] backports: add support for prandom_bytes
Date: Fri, 6 Dec 2013 19:26:01 +0100 [thread overview]
Message-ID: <20131206182601.GC8196@cerro.do-not-panic.com> (raw)
In-Reply-To: <20131206161531.GB8196@cerro.do-not-panic.com>
On Fri, Dec 06, 2013 at 05:15:31PM +0100, Luis R. Rodriguez wrote:
> On Tue, Dec 03, 2013 at 03:10:52PM +0100, Johannes Berg wrote:
> > +EXPORT_SYMBOL_GPL(prandom_bytes_state);
>
> Where is prandom_bytes_state defined? Did you mean prandom_bytes ?
> This breaks compilation right now.
I'll fix this upon merge, modifying this without _state fixed things.
Luis
next prev parent reply other threads:[~2013-12-06 18:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 14:10 [PATCH v3] backports: add support for prandom_bytes Johannes Berg
2013-12-06 16:15 ` Luis R. Rodriguez
2013-12-06 18:26 ` Luis R. Rodriguez [this message]
2013-12-08 7:28 ` Grumbach, Emmanuel
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=20131206182601.GC8196@cerro.do-not-panic.com \
--to=mcgrof@do-not-panic.com \
--cc=backports@vger.kernel.org \
--cc=emmanuel.grumbach@intel.com \
--cc=johannes@sipsolutions.net \
/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