Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762721AbYGOTl7 (ORCPT ); Tue, 15 Jul 2008 15:41:59 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758206AbYGOTlv (ORCPT ); Tue, 15 Jul 2008 15:41:51 -0400 Received: from mail.lang.hm ([64.81.33.126]:33983 "EHLO bifrost.lang.hm" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758127AbYGOTlu (ORCPT ); Tue, 15 Jul 2008 15:41:50 -0400 Date: Tue, 15 Jul 2008 12:41:44 -0700 (PDT) From: david@lang.hm X-X-Sender: dlang@asgard.lang.hm To: Linus Torvalds cc: Jeff Garzik , Henrique de Moraes Holschuh , Frans Pop , arjan@infradead.org, akpm@linux-foundation.org, dwmw2@infradead.org, alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org Subject: Re: [GIT *] Allow request_firmware() to be satisfied from in-kernel, use it in more drivers. In-Reply-To: Message-ID: References: <1216077806.27455.85.camel@shinybook.infradead.org> <20080714164119.99c33d5b.akpm@linux-foundation.org> <20080714165956.7fe2d4ee@infradead.org> <487C0365.5030203@garzik.org> <487C0365.5030203@garzik.org> <200807151757.10626.elendil@planet.nl> <20080715180535.GA6080@khazad-dum.debian.net> <487CE917.3000000@garzik.org> <487CF29E.5000009@garzik.org> User-Agent: Alpine 1.10 (DEB 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1392 Lines: 35 On Tue, 15 Jul 2008, Linus Torvalds wrote: > On Tue, 15 Jul 2008, Jeff Garzik wrote: >> >> Because people should not be forced to fix all their firmware-related breakage >> immediately, just to boot 2.6.27. > > You're continuing to make an argument that doesn't seem to backed up with > any actual real problems. > > Can you point to real breakage? For real people? several kernel devs ran into this with -next (Jeff can name names if needed) > It sounds like your whole argument literally boils down to "one or two > people doing something really stupid or odd cannot just fix their setup". > > What is the real-life situation where copying the firmware with the > modules (but still as separate files) actually breaks? > > IOW, what _is_ this theoretical breakage? And why is it so deadly > suddenly? Give us real examples that somehow cannot be fixed? there are no cases that cannot somehow be fixed. the desire is to make it possible to avoid having to find and fix everything before booting 2.6.27, while still making it possible to compile a kernel with all the new capabilities for those who want to fix everything now. David Lang -- 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/