From: Christoph Hellwig <hch@infradead.org>
To: James Smart <james.smart@emulex.com>
Cc: Daniel Borkmann <dborkman@redhat.com>,
davem@davemloft.net, netdev@vger.kernel.org,
James Bottomley <JBottomley@Parallels.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH net-next 2/2] random32: do not feed jiffies as seed from lpfc driver
Date: Mon, 11 Aug 2014 11:18:41 -0700 [thread overview]
Message-ID: <20140811181841.GA29747@infradead.org> (raw)
In-Reply-To: <282a2dc3-6381-42d6-ac34-81ceb56f1534@CMEXHTCAS2.ad.emulex.com>
On Mon, Aug 11, 2014 at 01:07:15PM -0400, James Smart wrote:
> Acked-by: James Smart <james.smart@emulex.com>
Can you jsut queue this up (and the pci fix as well) together with
anything else you have pending for 3.18?
I'd really like to move towards a model where maintainers of driver
collect everything for their area to spread work a bit better.
next prev parent reply other threads:[~2014-08-11 18:18 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
2014-08-11 17:07 ` James Smart
2014-08-11 18:18 ` Christoph Hellwig [this message]
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=20140811181841.GA29747@infradead.org \
--to=hch@infradead.org \
--cc=JBottomley@Parallels.com \
--cc=davem@davemloft.net \
--cc=dborkman@redhat.com \
--cc=james.smart@emulex.com \
--cc=linux-scsi@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).