From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760110AbXKBTzv (ORCPT ); Fri, 2 Nov 2007 15:55:51 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755044AbXKBTzm (ORCPT ); Fri, 2 Nov 2007 15:55:42 -0400 Received: from mailout.stusta.mhn.de ([141.84.69.5]:53173 "EHLO mailhub.stusta.mhn.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754307AbXKBTzl (ORCPT ); Fri, 2 Nov 2007 15:55:41 -0400 Date: Fri, 2 Nov 2007 20:55:17 +0100 From: Adrian Bunk To: David Brownell Cc: Randy Dunlap , Toralf =?utf-8?Q?F=C3=B6rster?= , linux-kernel@vger.kernel.org, netdev Subject: Re: build #337 failed for 2.6.24-rc1-gb1d08ac In function `usbnet_set_settings': Message-ID: <20071102195517.GW30287@stusta.de> References: <200711012024.57412.toralf.foerster@gmx.de> <200711021145.15542.david-b@pacbell.net> <20071102185751.GV30287@stusta.de> <200711021230.22588.david-b@pacbell.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <200711021230.22588.david-b@pacbell.net> User-Agent: Mutt/1.5.16 (2007-06-11) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Nov 02, 2007 at 12:30:22PM -0700, David Brownell wrote: > On Friday 02 November 2007, Adrian Bunk wrote: > > This approach has two disadvantages: > > - it's complicated > > No more so than the problem itself. > > > > - the MII stuff is an implementation detail, and we shouldn't bother > >   the user with it (especially since we can do better) > > That's a Kconfig policy that's not always followed. Sure it's not yet always followed. But kernel developers have to become more aware that the vast majority of kconfig users are not kernel hackers and act accordingly. I'm not talking about the infamous Aunt Tillie, but being able to build your own kernel is even required for LPIC-1. [1] > In this > case, I was getting fed up with "select". It so rarely does > what it needs to do, and I've started to think it'd be better > to just always avoid that fragility than battle it. Regarding this bug, "select" is completely innocent... > > If you want to keep the #ifdef's, what's the problem with the second > > patch I proposed to fix this bug? > > For one thing, I didn't see it until after I posted this one... > other than that, the basic approach could well be fine; I didn't > go through it in detail. > > But on the other hand, it seems that only the ASIX code will work > right; the DM9601 and MCS7830 Kconfig is different/wrong. I'm not seeing the problem. Which configuration will be handled wrongly? > - Dave cu Adrian [1] http://www.lpi.org/en/lpi/english/certification/the_lpic_program/exam_102_detailed_objectives -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed