Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755527AbYBGFn2 (ORCPT ); Thu, 7 Feb 2008 00:43:28 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754602AbYBGFnQ (ORCPT ); Thu, 7 Feb 2008 00:43:16 -0500 Received: from mx2.suse.de ([195.135.220.15]:58569 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751940AbYBGFnO (ORCPT ); Thu, 7 Feb 2008 00:43:14 -0500 Date: Wed, 6 Feb 2008 21:42:52 -0800 From: Greg KH To: Dhaval Giani Cc: Ingo Molnar , Peter Zijlstra , Kay Sievers , vatsa@linux.vnet.ibm.com, LKML , Balbir Singh , dmitry.adamushko@gmail.com, Steven Rostedt , Gregory Haskins , Thomas Gleixner , Andrew Morton Subject: Re: [PATCH 12/11] sched: rt-group: uid-group interface Message-ID: <20080207054252.GA20902@suse.de> References: <20080107122330.GB25945@linux.vnet.ibm.com> <1199725063.31975.53.camel@lappy> <20080108105733.GA2569@linux.vnet.ibm.com> <1199790150.7143.57.camel@twins> <3ae72650801080631p2b2c50a6q3d59badf06b62684@mail.gmail.com> <1199835332.31975.66.camel@lappy> <20080108235846.GA17067@suse.de> <20080108235750.GA27248@elte.hu> <20080110000531.GA18069@suse.de> <20080207041721.GA11520@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080207041721.GA11520@linux.vnet.ibm.com> User-Agent: Mutt/1.5.16 (2007-06-09) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1650 Lines: 41 On Thu, Feb 07, 2008 at 09:47:22AM +0530, Dhaval Giani wrote: > On Wed, Jan 09, 2008 at 04:05:31PM -0800, Greg KH wrote: > > > > > Ingo, Greg, > > > > > > > > > > What would be the easiest way to carry this forward? sched-devel and > > > > > greg's tree would intersect at this point and leave poor akpm with the > > > > > resulting mess. Should I just make an incremental patch akpm can carry > > > > > and push? Or can we base one tree off the other? > > > > > > > > If it's just a single patch for this, I'd be glad to take it. But by > > > > looking at the [11/12] above, I doubt this is so... > > > > > > > > If it's not that rough (12 patches is not a big deal), I'd be glad to > > > > take these through my tree, after you fix up Kay's requests above :) > > > > > > hm, i'd really like to see this tested and go through sched.git. It's > > > only the few sysfs bits which interfere, right? > > > > Yes, that should be it. > > > > So why not put the majority of this through sched.git, then when my > > sysfs changes go in at the beginning of the .25 merge cycle, you can > > then add the sysfs changes through your tree or anywhere else. > > > > Hi, > > I was wondering where these changes are right now. I don't see the sysfs > interface for rt-group-sched in mainline right now. All of the sysfs changes I had are in Linus's tree, so you don't need me anymore :) thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/