From: Rusty Russell <rusty@rustcorp.com.au>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: junio@siamese.dyndns.org, linux-scsi@vger.kernel.org
Subject: Re: [TRIVIAL] aic7xxx_Makefile fix
Date: Tue, 17 Dec 2002 10:12:20 +1100 [thread overview]
Message-ID: <20021216233429.53E752C2B4@lists.samba.org> (raw)
In-Reply-To: Your message of "Mon, 16 Dec 2002 15:30:03 MDT." <Pine.LNX.4.44.0212161527350.21707-100000@chaos.physics.uiowa.edu>
In message <Pine.LNX.4.44.0212161527350.21707-100000@chaos.physics.uiowa.edu> y
ou write:
> On Mon, 16 Dec 2002, Rusty Trivial Russell wrote:
>
> > From: junio@siamese.dyndns.org
> >
> > Patch against 2.4.19. If you are in a (good) habit of making
> > all the upstream sources read-only before starting your build,
> > generation of the firmware code fails because it tries to write
> > into read-only files. This bites only in configurations where
> > CONFIG_AIC7XXX_BUILD_FIRMWARE is set to 'y'.
> >
> >
> > --- trivial-2.4.21-pre1/drivers/scsi/aic7xxx/Makefile.orig 2002-12-16 17:22:40.000000000 +1100
> > +++ trivial-2.4.21-pre1/drivers/scsi/aic7xxx/Makefile 2002-12-16 17:22:40.000000000 +1100
> > @@ -39,6 +39,7 @@
> > $(obj-aic7xxx): aic7xxx_reg.h
> >
> > aic7xxx_seq.h aic7xxx_reg.h: aic7xxx.seq aic7xxx.reg aicasm/aicasm
> > + rm -f aic7xxx_seq.h aic7xxx_reg.h
> > aicasm/aicasm -I. -r aic7xxx_reg.h -o aic7xxx_seq.h aic7xxx.seq
> > endif
>
> This is 2.4, so I don't feel authorative for that ;) Anyhow, this is not a
> right fix (it's fixed properly in 2.5). Overwriting shipped files should
> never happen, the "rm" may fix the symptoms for some cases, but SCS as
> e.g. bitkeeper will generally not be happy with that kind of behavior.
Thanks Kai, I've closed it pending someone doing a backport from 2.5.
Cheers,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
prev parent reply other threads:[~2002-12-16 23:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 10:52 [TRIVIAL] aic7xxx_Makefile fix Rusty Trivial Russell
2002-12-16 21:30 ` Kai Germaschewski
2002-12-16 23:12 ` Rusty Russell [this message]
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=20021216233429.53E752C2B4@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=junio@siamese.dyndns.org \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-scsi@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