netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <jbottomley@parallels.com>
To: "dborkman@redhat.com" <dborkman@redhat.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, 1 Aug 2014 04:12:58 +0000	[thread overview]
Message-ID: <1406866378.5442.9.camel@jarvis> (raw)
In-Reply-To: <1406837317-13648-1-git-send-email-dborkman@redhat.com>

On Thu, 2014-07-31 at 22:08 +0200, Daniel Borkmann wrote:
> In prandom we have already reseeding mechanisms that trigger
> periodically from a much better entropy source than just
> feeding in jiffies through lpfc_mbx_cmpl_fcf_scan_read_fcf_rec()
> [what a function name 8-)]. Therefore, just remove this.
> 
> Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
> Cc: James Bottomley <JBottomley@Parallels.com>
> Cc: James Smart <james.smart@emulex.com>
> ---
>  This can also go via James, how you prefer it.

Could you send to linux-scsi@vger.kernel.org; Christoph Hellwig is
gathering patches for SCSI via that list.

Thanks,

James


  parent reply	other threads:[~2014-08-01  4:13 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 [this message]
2014-08-01 11:23   ` Daniel Borkmann
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=1406866378.5442.9.camel@jarvis \
    --to=jbottomley@parallels.com \
    --cc=davem@davemloft.net \
    --cc=dborkman@redhat.com \
    --cc=james.smart@emulex.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).