From: ebiederm@xmission.com (Eric W. Biederman)
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, Bill Pemberton <wfp5p@virginia.edu>
Subject: Re: [GIT PULL] user namespace compile fix for 3.7
Date: Wed, 03 Oct 2012 16:38:27 -0700 [thread overview]
Message-ID: <87fw5vyvm4.fsf@xmission.com> (raw)
In-Reply-To: <20121003232510.GC14392@kroah.com> (Greg Kroah-Hartman's message of "Wed, 3 Oct 2012 16:25:10 -0700")
Greg Kroah-Hartman <gregkh@linuxfoundation.org> writes:
> On Wed, Oct 03, 2012 at 04:03:54PM -0700, Eric W. Biederman wrote:
>>
>> Linus,
>>
>> Please pull the for-linus git tree from:
>>
>> git://git.kernel.org:/pub/scm/linux/kernel/git/ebiederm/user-namespace.git for-linus
>>
>> HEAD: 702e490211b2b7e448ebe1b3a07d97ad2fc07e03 userns: Fix build of drivers/staging/dgrp
>>
>> This tree contains a trivial build fix for one of the staging drivers
>> when user namespace support is enabled.
>
> Is this something new? Why didn't it show up in the linux-next builds?
Yes this appears to have been a silent merge conflict between my user
namespace tree and your staging tree.
I care because it breaks my builds.
This build failure only shows up when CONFIG_USER_NS is enabled which
would have required a randconfig build in linux-next for it to show up.
When I get the last of the filesystems converted for 3.8 this kind of
failure should stop hiding in the more customary build checks.
> I'll be glad to take this single patch myself and queue it up with other
> staging tree fixes before 3.7-final is out, what is the big rush?
I figured I found it, I fixed it, and I am going to be carrying the fix
anyway in my tree, so why not make it easy on everyone and make it a
patch that can be pulled.
Eric
prev parent reply other threads:[~2012-10-03 23:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 23:03 [GIT PULL] user namespace compile fix for 3.7 Eric W. Biederman
2012-10-03 23:25 ` Greg Kroah-Hartman
2012-10-03 23:38 ` Eric W. Biederman [this message]
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=87fw5vyvm4.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=wfp5p@virginia.edu \
/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