From: Daniel Borkmann <dborkman@redhat.com>
To: James Bottomley <jbottomley@parallels.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"james.smart@emulex.com" <james.smart@emulex.com>
Subject: Re: [PATCH net-next 2/2] random32: do not feed jiffies as seed from lpfc driver
Date: Fri, 01 Aug 2014 13:23:14 +0200 [thread overview]
Message-ID: <53DB78A2.4090504@redhat.com> (raw)
In-Reply-To: <1406866378.5442.9.camel@jarvis>
On 08/01/2014 06:12 AM, James Bottomley wrote:
...
> Could you send to linux-scsi@vger.kernel.org; Christoph Hellwig is
> gathering patches for SCSI via that list.
Sure, done, thanks.
next prev parent reply other threads:[~2014-08-01 11:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 20:08 [PATCH net-next 2/2] random32: do not feed jiffies as seed from lpfc driver Daniel Borkmann
2014-07-31 20:11 ` David Miller
2014-08-01 4:12 ` James Bottomley
2014-08-01 11:23 ` Daniel Borkmann [this message]
2014-08-11 17:07 ` James Smart
2014-08-11 18:18 ` Christoph Hellwig
2014-08-11 18:38 ` James Smart
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=53DB78A2.4090504@redhat.com \
--to=dborkman@redhat.com \
--cc=davem@davemloft.net \
--cc=james.smart@emulex.com \
--cc=jbottomley@parallels.com \
--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;
as well as URLs for NNTP newsgroup(s).