From: junio@siamese.dyndns.org
To: linux-kernel@vger.kernel.org
Cc: trivial@rustcorp.com.au
Subject: [TRIVIAL] aic7xxx/Makefile fix
Date: 28 Aug 2002 14:21:27 -0700 [thread overview]
Message-ID: <7vit1ullwo.fsf@siamese.dyndns.org> (raw)
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'.
--- 2.4.19/drivers/scsi/aic7xxx/Makefile 2002-08-02 10:48:53.000000000 -0700
+++ 2.4.19/drivers/scsi/aic7xxx/Makefile 2002-08-28 14:14:31.000000000 -0700
@@ -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
reply other threads:[~2002-08-28 21:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=7vit1ullwo.fsf@siamese.dyndns.org \
--to=junio@siamese.dyndns.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@rustcorp.com.au \
/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;
as well as URLs for NNTP newsgroup(s).