From: "J . A . Magallon" <jamagallon@able.es>
To: Keith Owens <kaos@ocs.com.au>
Cc: "Justin T . Gibbs" <gibbs@scsiguy.com>, linux-kernel@vger.kernel.org
Subject: Re: Cleanup kbuild for aic7xxx
Date: Sat, 23 Jun 2001 03:20:47 +0200 [thread overview]
Message-ID: <20010623032047.A14928@werewolf.able.es> (raw)
In-Reply-To: <200106221939.f5MJdjU78255@aslan.scsiguy.com> <10972.993257428@ocs3.ocs-net>
In-Reply-To: <10972.993257428@ocs3.ocs-net>; from kaos@ocs.com.au on Sat, Jun 23, 2001 at 02:50:28 +0200
On 20010623 Keith Owens wrote:
>
>>What again are you trying to fix? It looks to me like you are simply
>>trying to make it harder for people actually working on the aic7xxx
>>driver to have proper dependencies.
>
>The patch still works for anybody changing the aic7xxx firmware or the
>aicasm code. Any change to the generated files or the aicasm files now
>forces a rebuild, the option is not required. Only people changing
>aic7xxx firmware are affected, instead of everybody.
>
It is easier than that. Nobody should be rebuilding the firmware apart
from driver mantainers. If driver version in 2.4.5 is 6.1.13, that version
includes a certain firmware in .h format and that is all. Apart from
this, the author (Justin) can make available in his web page one other
package for driver testers or developers including aicasm and firmware
source. But that should not be in the kernel tree.
If there are updates to the firmware, just send the patch for .h files
to kernel mantainers and/or lkml, as everybody does.
This is easier, doesn't it ?
--
J.A. Magallon # Let the source be with you...
mailto:jamagallon@able.es
Mandrake Linux release 8.1 (Cooker) for i586
Linux werewolf 2.4.5-ac17 #2 SMP Fri Jun 22 01:36:07 CEST 2001 i686
next prev parent reply other threads:[~2001-06-23 1:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-22 17:52 Cleanup kbuild for aic7xxx Keith Owens
2001-06-22 19:39 ` Justin T. Gibbs
2001-06-23 0:50 ` Keith Owens
2001-06-23 1:20 ` J . A . Magallon [this message]
2001-06-23 1:54 ` Keith Owens
2001-06-23 2:38 ` Justin T. Gibbs
2001-06-23 4:19 ` D. Stimits
2001-06-23 1:32 ` David Ford
2001-06-23 2:46 ` Justin T. Gibbs
2001-06-23 2:57 ` David Ford
2001-06-23 3:07 ` Justin T. Gibbs
2001-06-23 3:57 ` David Ford
2001-06-23 5:10 ` Justin T. Gibbs
2001-06-23 4:41 ` David Ford
2001-06-23 5:11 ` Justin T. Gibbs
2001-06-23 5:58 ` [working] Re: Cleanup kbuild for aic7xxx (attn: Alan & Doug) David Ford
2001-06-23 4:58 ` Cleanup kbuild for aic7xxx David Ford
2001-06-23 2:34 ` Justin T. Gibbs
2001-06-23 5:22 ` Keith Owens
2001-06-25 18:22 ` Justin T. Gibbs
2001-06-26 2:34 ` Keith Owens
2001-06-26 4:27 ` Justin T. Gibbs
2001-06-23 4:17 ` D. Stimits
2001-06-23 4:54 ` Keith Owens
2001-06-23 5:14 ` Justin T. Gibbs
2001-06-23 5:34 ` Keith Owens
2001-06-23 5:04 ` Justin T. Gibbs
2001-06-23 5:41 ` D. Stimits
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010623032047.A14928@werewolf.able.es \
--to=jamagallon@able.es \
--cc=gibbs@scsiguy.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox