[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m1zkzyfdob.fsf@fess.ebiederm.org>
Date: Mon, 17 May 2010 13:58:44 -0700
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Greg KH <greg@...ah.com>
Cc: David Miller <davem@...emloft.net>, gregkh@...e.de,
kay.sievers@...y.org, linux-kernel@...r.kernel.org, tj@...nel.org,
cornelia.huck@...ibm.com, eric.dumazet@...il.com, bcrl@...et.ca,
serue@...ibm.com, netdev@...r.kernel.org
Subject: Re: [PATCH 0/6] netns support in the kobject layer
Greg KH <greg@...ah.com> writes:
> On Sat, May 15, 2010 at 11:26:43PM -0700, David Miller wrote:
>> From: Greg KH <greg@...ah.com>
>> Date: Thu, 6 May 2010 13:04:04 -0700
>>
>> > On Tue, May 04, 2010 at 05:35:54PM -0700, Eric W. Biederman wrote:
>> >>
>> >> With the tagged sysfs support finally merged into Greg's tree,
>> >> it is time for the last little bits of work to get the kobject
>> >> layer and network namespaces to play together properly.
>> >>
>> >> These patches are roughly evenly divided between network layer work
>> >> and sysfs layer work. Last time this conundrum came up I believe
>> >> we decided that the easiest way to handle this was for Greg to carry
>> >> all of the patches. David, Greg does that still make sense?
>> >
>> > That's fine, if I get David's ack on these.
>>
>> Looks good to me:
>>
>> Acked-by: David S. Miller <davem@...emloft.net>
>
> Ok. Eric, can you resend these to me when .35-rc1 is out so I can queue
> them up then to get some testing in linux-next so that they can make it
> into .36?
Grumble. Grumble. Grumble.
If I must I will resend these, but these patches are already in
production use, and I had them to you weeks before the merge window
closed.
Is there no way we can get these in for 2.6.35?
Eric
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists