From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Hansen Subject: Re: Feeding containers patches into linux-next Date: Tue, 15 Jul 2008 12:07:52 -0700 Message-ID: <1216148872.25942.13.camel@nimitz> References: <1216133004.8856.53.camel@nimitz> <20080715152933.GA12061@us.ibm.com> <1216144516.9459.7.camel@nimitz> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: "Eric W. Biederman" Cc: Containers List-Id: containers.vger.kernel.org On Tue, 2008-07-15 at 11:56 -0700, Eric W. Biederman wrote: > Dave Hansen writes: > > On Tue, 2008-07-15 at 10:50 -0700, Eric W. Biederman wrote: > >> The classic challenge is that we really need most of the patches to go > >> through other maintainers because they are not for subsystems we > >> maintain. So I am fairly certain things like our network namespace > >> work will show up in linux-next because they show up in net-next-2.6. > > > > But, there are things like the mqueue patches that are against areas > > that really have no maintainers. Do you think there will be many more > > like that? > > Probably. We are touching parts of the kernel that rarely change. Would having something that feeds into linux-next help make some of this easier? -- Dave