netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: andi@firstfloor.org
Cc: netdev@vger.kernel.org
Subject: Re: [PING^2] [PATCH] srandom32 fixes for networking
Date: Wed, 02 Apr 2008 01:20:22 -0700 (PDT)	[thread overview]
Message-ID: <20080402.012022.106064938.davem@davemloft.net> (raw)
In-Reply-To: <20080402082103.GN29105@one.firstfloor.org>

From: Andi Kleen <andi@firstfloor.org>
Date: Wed, 2 Apr 2008 10:21:03 +0200

> On Wed, Apr 02, 2008 at 01:03:24AM -0700, David Miller wrote:
> > From: Andi Kleen <andi@firstfloor.org>
> > Date: Wed, 2 Apr 2008 09:50:11 +0200
> > 
> > > Can you send me your config please? I don't see any build problem
> > > here with the patch on top of -rc7-git something on either i386 nor x86-64.
> > 
> > I found it with "git grep srandom32", I guess I'm quite old school in
> > that I actually check the tree when interfaces are being changed.
> 
> Ah I see the problem now.  The patch requires 
> 
> ftp://firstfloor.org/pub/ak/misc/patches/pageattr-own-random
> 
> applied first to remove this reference. Sorry should 
> have made that more clear.  The original post had both
> patches, but in the reposts the reference to the dependency
> got dropped somehow, sorry.

You have to decide how to submit this without introducing
the build failure then.

I would suggest getting your first change in, and when that
happens, resubmit this one.

  reply	other threads:[~2008-04-02  8:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01 11:34 [PING^2] [PATCH] srandom32 fixes for networking Andi Kleen
2008-04-02  7:18 ` David Miller
2008-04-02  7:50   ` Andi Kleen
2008-04-02  8:03     ` David Miller
2008-04-02  8:21       ` Andi Kleen
2008-04-02  8:20         ` David Miller [this message]
2008-04-02  9:44           ` Andi Kleen

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=20080402.012022.106064938.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=andi@firstfloor.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).