From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: David Howells <dhowells@redhat.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
lkml <linux-kernel@vger.kernel.org>,
jmorris@us.ibm.com
Subject: Re: [PATCH] User namespaces: set of cleanups (v2)
Date: Tue, 28 Oct 2008 11:21:59 -0500 [thread overview]
Message-ID: <20081028162159.GA15342@us.ibm.com> (raw)
In-Reply-To: <20081025130531.ca063206.sfr@canb.auug.org.au>
Quoting Stephen Rothwell (sfr@canb.auug.org.au):
> Hi Serge,
>
> On Fri, 24 Oct 2008 12:48:38 -0500 "Serge E. Hallyn" <serue@us.ibm.com> wrote:
> >
> > would you mind applying the patch below behind
> > git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/cred-2.6.git#creds-v3?
> >
> > Assuming David has no objections?
> >
> > I've just tested with David's plain creds-v3 tree and had no problems.
> > (compiled with CONFIG_USER_NS=y|n and CONFIG_KEYS=y|n, boot+ltp with
> > both =y)
> >
> > Or would it fit your model better if I found a place to keep a quilt
> > patchset or git tree?
>
> Better if you can set up a git tree (or quilt series) somewhere as I
> intend to only carry fixup patches myself in linux-next (so far). Also
> that means when you update your patches, I will just fetch them
> automatically.
The tree is up at:
git://git.kernel.org/pub/scm/linux/kernel/git/sergeh/userns-2.6#next
with just two patches on top of David's creds-v4.
> If this stuff depends on David's work, then I need to know that
> explicitly so I can do ordering. If it depends closely (i.e. changes in
Yes it belongs after his creds-v4 tree.
> Davids tree need to be reflected in yours) then you and David need to
> come to some arrangement (maybe David could host your tree as a branch of
> his (managing conflicts/updates).
I don't know how many additional changes David plans to make in the near
future. Assuming he makes them in creds-v4 and not in a new tree I
guess I'll feel the pain but that's how it goes.
Any additional userns patches would likely be feature enhancements and
I don't expect to get them in any kindo f merge-worthy shape before
2.6.29 is out.
thanks,
-serge
next prev parent reply other threads:[~2008-10-28 16:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 17:48 [PATCH] User namespaces: set of cleanups (v2) Serge E. Hallyn
2008-10-24 18:44 ` David Howells
2008-10-24 19:18 ` Serge E. Hallyn
2008-10-24 19:40 ` David Howells
2008-10-25 2:08 ` Stephen Rothwell
2008-10-26 11:07 ` David Howells
2008-10-26 11:53 ` Stephen Rothwell
2008-10-26 16:04 ` David Howells
2008-10-26 16:11 ` David Howells
2008-10-25 2:05 ` Stephen Rothwell
2008-10-28 16:21 ` Serge E. Hallyn [this message]
2008-10-29 7:36 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2008-10-20 23:01 Serge E. Hallyn
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=20081028162159.GA15342@us.ibm.com \
--to=serue@us.ibm.com \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=jmorris@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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