From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 21 May 2002 01:09:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 21 May 2002 01:09:26 -0400 Received: from aslan.scsiguy.com ([63.229.232.106]:34318 "EHLO aslan.scsiguy.com") by vger.kernel.org with ESMTP id ; Tue, 21 May 2002 01:09:25 -0400 Message-Id: <200205210507.g4L570948949@aslan.scsiguy.com> To: Kai Germaschewski cc: Peter Chubb , trivial@rustcorp.com.au, linux-kernel@vger.kernel.org Subject: Re: Allow aic7xx firmware to be built from BK tree. In-Reply-To: Your message of "Mon, 20 May 2002 23:48:56 CDT." Date: Mon, 20 May 2002 23:07:00 -0600 From: "Justin T. Gibbs" Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org >On Mon, 20 May 2002, Justin T. Gibbs wrote: > >> >This patch removes the two generate files (that are also in the >> >distributed kernel) before attempting to regenerate them. >> >> Why is this necessary? > >Well, I'll take Keith Owen's role and answer: > >Some people are using source control management systems which >leave the managed files read-only. These people shouldn't be rebuilding the firmware. 8-) >Some developers use bitkeeper these days, and it'll show exactly this >problem. I suppose the only reason that not more people complain about it >is that hardly anyone has set CONFIG_AIC7XXX_BUILD_FIRMWARE=y. Which is the default. Those enabling this feature get what they get as is documented in Configure.help (or at least was in 2.4.X). >The correct way to fix this is to not overwrite the shipped files. The >appended patch is a suggestion on how to avoid the mentioned problems. >(I should pay credit to Keith Owens, since he proposed a similar solution >before) Only with lots of MD5 junk and other complicated rules. I have no problem with changing the name of the shipped files and using a link if that will finally put this issue to rest. -- Justin