Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932364AbWBBWcW (ORCPT ); Thu, 2 Feb 2006 17:32:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932368AbWBBWcW (ORCPT ); Thu, 2 Feb 2006 17:32:22 -0500 Received: from mx1.redhat.com ([66.187.233.31]:27025 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S932367AbWBBWcV (ORCPT ); Thu, 2 Feb 2006 17:32:21 -0500 Date: Thu, 2 Feb 2006 17:31:56 -0500 From: Dave Jones To: Sam Ravnborg Cc: Michael Loftis , David Weinehall , Doug McNaught , Russell King , Valdis.Kletnieks@vt.edu, dtor_core@ameritech.net, James Courtier-Dutton , linux-kernel@vger.kernel.org Subject: Re: Development tree, PLEASE? Message-ID: <20060202223156.GK11831@redhat.com> Mail-Followup-To: Dave Jones , Sam Ravnborg , Michael Loftis , David Weinehall , Doug McNaught , Russell King , Valdis.Kletnieks@vt.edu, dtor_core@ameritech.net, James Courtier-Dutton , linux-kernel@vger.kernel.org References: <20060120200051.GA12610@flint.arm.linux.org.uk> <5793EB6F192350088E0AC4CE@d216-220-25-20.dynip.modwest.com> <87slrio9wd.fsf@asmodeus.mcnaught.org> <25D702FB62516982999D7084@d216-220-25-20.dynip.modwest.com> <20060202121653.GI20484@vasa.acc.umu.se> <67A0AFFBC77C32B9DEE25EFA@dhcp-2-206.wgops.com> <20060202201008.GD11831@redhat.com> <20060202220519.GA8712@mars.ravnborg.org> <20060202221023.GJ11831@redhat.com> <20060202221922.GB8712@mars.ravnborg.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060202221922.GB8712@mars.ravnborg.org> User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1095 Lines: 24 On Thu, Feb 02, 2006 at 11:19:22PM +0100, Sam Ravnborg wrote: > > -rw-r--r-- 1 davej davej 1753 Dec 15 23:31 linux-2.6-bzimage.patch > > > > To get around some gynamstics in the rpm spec, defining a seperate build target > > for every arch, we make every arch grok 'bzImage'. Fugly, but it keeps the > > spec cleaner to maintain. > > Yup - seen it before. Did not like it. > Consistent use of KBUILD_IMAGE across relevant architectures should buy > you the same simplicity and a mergeable approach. tbh, patches like this just sit there, as 'they just work', rarely need rediffing, the benefit to other people of it being upstream are next to nil (or someone else would've done it by now), and I'm more motivated to work on real problems like finding out why we've 3 different flavours of slab corruption right now. Dave - 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/