From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761120AbYGRUWm (ORCPT ); Fri, 18 Jul 2008 16:22:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757016AbYGRUWb (ORCPT ); Fri, 18 Jul 2008 16:22:31 -0400 Received: from out01.mta.xmission.com ([166.70.13.231]:44161 "EHLO out01.mta.xmission.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751814AbYGRUWa (ORCPT ); Fri, 18 Jul 2008 16:22:30 -0400 From: ebiederm@xmission.com (Eric W. Biederman) To: Greg KH Cc: Tejun Heo , Andrew Morton , Daniel Lezcano , linux-kernel@vger.kernel.org, Al Viro , Linux Containers , Benjamin Thery , netdev@vger.kernel.org References: <486DD650.3000804@gmail.com> <486E2C3B.6020603@gmail.com> <20080704161200.GA1440@suse.de> <487D6A24.9070001@gmail.com> <20080717230857.GB28377@suse.de> <48808F79.7080607@gmail.com> <20080718184936.GA21343@suse.de> Date: Fri, 18 Jul 2008 13:19:55 -0700 In-Reply-To: <20080718184936.GA21343@suse.de> (Greg KH's message of "Fri, 18 Jul 2008 11:49:36 -0700") Message-ID: User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SA-Exim-Connect-IP: 24.130.11.59 X-SA-Exim-Mail-From: ebiederm@xmission.com X-Spam-DCC: XMission; sa02 1397; Body=1 Fuz1=1 Fuz2=1 X-Spam-Combo: ;Greg KH X-Spam-Relay-Country: X-Spam-Report: * -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP * 0.0 T_TM2_M_HEADER_IN_MSG BODY: T_TM2_M_HEADER_IN_MSG * -0.7 BAYES_20 BODY: Bayesian spam probability is 5 to 20% * [score: 0.1082] * -0.0 DCC_CHECK_NEGATIVE Not listed in DCC * [sa02 1397; Body=1 Fuz1=1 Fuz2=1] * 0.0 XM_SPF_Neutral SPF-Neutral Subject: Re: [PATCH 12/15] driver core: Implement tagged directory support for device classes. X-SA-Exim-Version: 4.2 (built Thu, 03 Mar 2005 10:44:12 +0100) X-SA-Exim-Scanned: Yes (on mgr1.xmission.com) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Greg KH writes: > On Fri, Jul 18, 2008 at 09:41:29PM +0900, Tejun Heo wrote: >> Greg KH wrote: >> > Ok, I'll work to get these in where applicable. >> >> Did this get into 2.6.27? Or will this have to wait till .28? > > I haven't sent any patches to Linus yet for 2.6.27, so it hasn't gotten > there yet. > > And due to the intrusiveness, and the fact that this hasn't been tested > at all in any build tree yet, I can't in good concious submit this for > .27 either. > > Part of this is my fault, I know, due to vacation and work, but also > lots is due to the fact that the code showed up so late in the > development cycle. The code showed up at least by the beginning of may, and the code has been around for 9 months or more. I just haven't always had the energy to retransmit every time it has gotten dropped. The last spin of it was very late I agree. > I'll add it to my tree, and get it some testing in the next cycle of > linux-next until 2.6.27 is out, and then if it's still looking good, go > into .28. I think that is unnecessarily precautions but reasonable. That should at least keep other sysfs patches from coming in and causing bit rot. Eric