Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756454AbYGCNjA (ORCPT ); Thu, 3 Jul 2008 09:39:00 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755259AbYGCNip (ORCPT ); Thu, 3 Jul 2008 09:38:45 -0400 Received: from srv5.dvmed.net ([207.36.208.214]:51963 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755248AbYGCNio (ORCPT ); Thu, 3 Jul 2008 09:38:44 -0400 Message-ID: <486CD654.4020605@garzik.org> Date: Thu, 03 Jul 2008 09:38:28 -0400 From: Jeff Garzik User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: David Woodhouse CC: Hugh Dickins , Andrew Morton , KOSAKI Motohiro , mchan@broadcom.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, netdev@vger.kernel.org Subject: Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" References: <20080703020236.adaa51fa.akpm@linux-foundation.org> <20080703205548.D6E5.KOSAKI.MOTOHIRO@jp.fujitsu.com> <486CC440.9030909@garzik.org> <486CCFED.7010308@garzik.org> <1215091999.10393.556.camel@pmac.infradead.org> In-Reply-To: <1215091999.10393.556.camel@pmac.infradead.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -4.3 (----) X-Spam-Report: SpamAssassin version 3.2.4 on srv5.dvmed.net summary: Content analysis details: (-4.3 points, 5.0 required) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1201 Lines: 32 David Woodhouse wrote: >> dwmw2 has been told repeatedly that his changes will cause PRECISELY >> these problems, but he refuses to take the simple steps necessary to >> ensure people can continue to boot their kernels after his changes go in. > > Complete nonsense. Setting CONFIG_FIRMWARE_IN_KERNEL isn't hard. But > shouldn't be the _default_, either. > >> Presently his tg3 changes have been nak'd, in part, because of this >> obviously, forseeable, work-around-able breakage. > > They haven't even been reviewed. Nobody seems to have actually looked at Yes, they have. You just didn't like the answers you received. In particular, the Kconfig default for built-in tg3 firmware should result in the current behavior, without the user having to take extra steps. Because of your stubborn refusal on this Kconfig defaults issue, WE ALREADY HAVE DRIVER-DOES-NOT-WORK BREAKAGE, JUST AS PREDICTED. Wake up and smell reality. Please. Jeff -- 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/