From: David Miller <davem@davemloft.net>
To: sfr@canb.auug.org.au
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
paul.moore@hp.com, jmorris@namei.org, mst@redhat.com
Subject: Re: linux-next: security-testing/net tree build failure
Date: Sun, 13 Sep 2009 21:46:44 -0700 (PDT) [thread overview]
Message-ID: <20090913.214644.164044855.davem@davemloft.net> (raw)
In-Reply-To: <20090914130154.8b6df8f9.sfr@canb.auug.org.au>
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Mon, 14 Sep 2009 13:01:54 +1000
> On Thu, 3 Sep 2009 16:14:32 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>
>> Today's linux-next build (powerpc ppc64_defconfig) failed like this (this
>> was reverting to the security-testing tree in next-20090902):
>>
>> drivers/net/tun.c: In function 'tun_set_iff':
>> drivers/net/tun.c:937: error: 'struct tun_struct' has no member named 'sk'
>>
>> Caused by commit 2b980dbd77d229eb60588802162c9659726b11f4 ("lsm: Add
>> hooks to the TUN driver") interacting with commit
>> 89f56d1e91cfa535ccc6cc60e9e12e02682fd972 ("tun: reuse struct sock
>> fields") from the net tree.
>>
>> I applied the following merge fix patch (which I can carry as necessary):
>
> This patch now needs to be applied to the net tree (as the
> security-testing tree has been merged by Linus). I have applied it as a
> merge fix for today.
Ok, since I already sent a merge request to Linus I'll submit this
as soon as he does that pull.
I don't like "slipping" in things to a tree I've already asked
him to pull from, and in this case especially since I'd have
to merge his tree in to keep net-next-2.6 itself building.
:-)
next prev parent reply other threads:[~2009-09-14 4:46 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 ` linux-next: security-testing/net tree build failure David Miller
2009-09-03 13:10 ` 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 [this message]
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=20090913.214644.164044855.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).