From: David Miller <davem@davemloft.net>
To: sfr@canb.auug.org.au
Cc: jmorris@namei.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, paul.moore@hp.com, mst@redhat.com
Subject: Re: linux-next: security-testing/net tree build failure
Date: Wed, 02 Sep 2009 23:16:07 -0700 (PDT) [thread overview]
Message-ID: <20090902.231607.200932036.davem@davemloft.net> (raw)
In-Reply-To: <20090903161432.44af630d.sfr@canb.auug.org.au>
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Thu, 3 Sep 2009 16:14:32 +1000
> I applied the following merge fix patch (which I can carry as necessary):
Looks good from here, thanks Stephen.
next parent reply other threads:[~2009-09-03 6:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090903161432.44af630d.sfr@canb.auug.org.au>
2009-09-03 6:16 ` David Miller [this message]
2009-09-03 13:10 ` linux-next: security-testing/net tree build failure Paul Moore
2009-09-03 13:31 ` Stephen Rothwell
2009-09-07 10:59 ` Michael S. Tsirkin
[not found] ` <20090914130154.8b6df8f9.sfr@canb.auug.org.au>
2009-09-14 4:46 ` David Miller
2009-09-14 4:56 ` Stephen Rothwell
2009-09-14 5:01 ` David Miller
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=20090902.231607.200932036.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mst@redhat.com \
--cc=paul.moore@hp.com \
--cc=sfr@canb.auug.org.au \
/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).