All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cedric Le Goater <clg@fr.ibm.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: David Miller <davem@davemloft.net>,
	containers@lists.osdl.org, netdev@vger.kernel.org,
	akpm@linux-foundation.org
Subject: Re: [PATCH] net: Add network namespace clone & unshare support.
Date: Fri, 28 Sep 2007 11:12:13 +0200	[thread overview]
Message-ID: <46FCC56D.9050600@fr.ibm.com> (raw)
In-Reply-To: <m18x6rhfy0.fsf@ebiederm.dsl.xmission.com>

Eric W. Biederman wrote:
> David Miller <davem@davemloft.net> writes:
> 
>> Eric, pick an appropriate new non-conflicting number NOW.
> 
> Done.  My apologies for the confusion.  I thought the
> way Cedric and the IBM guys were testing someone would have
> shouted at me long before now.
>
>> This adds unnecessary extra work for Andrew Morton, which he has
>> enough of already.
> 
> Cedric made a good point that we will have conflicts of code
> being added to the same place in nsproxy.c and the like.  So
> I copied Andrew to give him a heads up.

here's a suggestion,

we could keep the net namespace unshare patch out of david's tree,
let andrew merge and release a new -mm and, then, send the net namespace 
unshare patch to andrew. that should keep nsproxy out of the andrew's 
merge challenge. But david's tree will miss the unshare part for a while.

As for the clone flags, the values *must not* conflict but the patches 
probably will.

C.

> I will gladly do what I can, to help.  Working against 3 trees
> development at the moment is a bit of a development challenge.
> 
> Eric
> _______________________________________________
> Containers mailing list
> Containers@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/containers
> 


  parent reply	other threads:[~2007-09-28  9:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-26 23:49 [PATCH] net: Add network namespace clone & unshare support Eric W. Biederman
2007-09-27  5:04 ` David Miller
2007-09-27  8:51 ` Cedric Le Goater
2007-09-27 17:14   ` Eric W. Biederman
2007-09-27 19:45     ` David Miller
2007-09-27 23:00       ` Eric W. Biederman
2007-09-28  0:10         ` David Miller
2007-09-28  0:25           ` Andrew Morton
2007-09-28  3:28             ` Eric W. Biederman
2007-09-28  4:26               ` David Miller
     [not found]         ` <m18x6rhfy0.fsf-T1Yj925okcoyDheHMi7gv2pdwda3JcWeAL8bYrjMMd8@public.gmane.org>
2007-09-28  0:53           ` Mark Nelson
     [not found]             ` <46FC50A6.1040302-8fk3Idey6ehBDgjK7y7TUQ@public.gmane.org>
2007-09-28  9:16               ` Cedric Le Goater
2007-09-28  9:12         ` Cedric Le Goater [this message]
2007-09-28  9:28           ` Andrew Morton
2007-09-28 11:56             ` Cedric Le Goater

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=46FCC56D.9050600@fr.ibm.com \
    --to=clg@fr.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=containers@lists.osdl.org \
    --cc=davem@davemloft.net \
    --cc=ebiederm@xmission.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.