Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932624Ab0GOHzk (ORCPT ); Thu, 15 Jul 2010 03:55:40 -0400 Received: from cantor.suse.de ([195.135.220.2]:50858 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932570Ab0GOHzj (ORCPT ); Thu, 15 Jul 2010 03:55:39 -0400 Date: Thu, 15 Jul 2010 00:56:11 -0700 From: Greg KH To: Dave Airlie Cc: Andrew Morton , Jens Axboe , Randy Dunlap , alsa-devel@alsa-project.org, Peter Zijlstra , linux-scsi@vger.kernel.org, Takashi Iwai , Greg KH , Kay Sievers , linux-kernel@vger.kernel.org, David Howells , "James E.J. Bottomley" , Alan Stern , "Eric W. Biederman" , Ingo Molnar , Tejun Heo , Alexey Kuznetsov , Stephen Hemminger , "David S. Miller" Subject: Re: [alsa-devel] [PATCH] driver core: remove CONFIG_SYSFS_DEPRECATED Message-ID: <20100715075611.GB8202@suse.de> References: <20100709185450.GA29473@kroah.com> <20100714163852.b3c09930.akpm@linux-foundation.org> <20100715041400.GA2583@suse.de> <20100715053543.GA4416@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2143 Lines: 52 On Thu, Jul 15, 2010 at 04:32:46PM +1000, Dave Airlie wrote: > On Thu, Jul 15, 2010 at 3:35 PM, Greg KH wrote: > > On Thu, Jul 15, 2010 at 03:00:31PM +1000, Dave Airlie wrote: > >> On Thu, Jul 15, 2010 at 2:14 PM, Greg KH wrote: > >> > On Thu, Jul 15, 2010 at 10:24:18AM +1000, Dave Airlie wrote: > >> >> On Thu, Jul 15, 2010 at 9:38 AM, Andrew Morton > >> >> wrote: > >> >> > On Fri, 9 Jul 2010 11:54:50 -0700 > >> >> > Greg Kroah-Hartman wrote: > >> >> > > >> >> >> This is no longer needed by any userspace tools, so it's safe to > >> >> >> remove. > >> >> > >> >> Also still used for booting mainline kernels on RHEL5 userspaces. > >> > > >> > Really? ?I thought that was fixed a long time ago. ?What kernel was > >> > RHEL5 originally based on? > >> > > >> > And note that no RHEL5 user is going to be using a .36 kernel on their > >> > system, that's a completely unsupported and unadvised situation. ?Heck, > >> > I'd be amazed if a .34 kernel.org kernel boots on the thing, does it? > >> > > >> > >> I think some people do it internally, last time I did it was to test > >> something I was backporting, so you want to make sure the upstream > >> version boots and the backported version also boots on the same > >> hw/userspace. > >> > >> original kernel was 2.6.18. > > > > Yes, that was the number, but does it really look anything like a .18 > > kernel.org release? ?:) > > > > Well its more that the userspace is mostly what was released at the > same time, we aren't going to update udev/mkinitrd unless some major > problem was discovered. That's fine, I can provide an updated package for those looney users that want to run this type of system :) But ideally, I can figure out what is being needed and possibly reduce the footprint that is currently covered by this config option. 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/