From: Keith Owens <kaos@ocs.com.au>
To: linux-kernel@vger.kernel.org
Subject: 2.4.7-ac9 drivers/scsci/Makefile cpqfc
Date: Wed, 08 Aug 2001 23:24:46 +1000 [thread overview]
Message-ID: <2694.997277086@ocs3.ocs-net> (raw)
This chunk of code in 2.4.7-ac9 drivers/scsi/Makefile makes no sense.
#if we have a triggerable HBA (extra circuit addition for
#TTL level output on GPIO line), build in the trigger file
#CPQTRIGGER_FILE = cpqfcTStrigger.c
CPQTRIG = cpqfcTStrigger.o
cpqfcTStrigger.o: cpqfcTStrigger.c
cpqfcTSinit.o: cpqfcTSinit.c cpqfcTSstructs.h cpqfcTSchip.h cpqfcTSioctl.h
cpqfcTScontrol.o: cpqfcTScontrol.c cpqfcTSstructs.h cpqfcTSchip.h
cpqfcTSi2c.o: cpqfcTSi2c.c cpqfcTSchip.h
cpqfcTSworker.o: cpqfcTSworker.c cpqfcTSchip.h cpqfcTSstructs.h cpqfcTSioctl.h
cpqfc.o: cpqfcTSinit.o cpqfcTScontrol.o cpqfcTSi2c.o cpqfcTSworker.o $(CPQTRIG)
$(LD) -r -o cpqfc.o cpqfcTSinit.o cpqfcTScontrol.o \
cpqfcTSi2c.o cpqfcTSworker.o $(CPQTRIG)
Why are all the individual dependencies listed, make dep does it
automatically. Why is cpqfc not coded like this?
list-multi += cpqfc.o
cpqfc-objs := cpqfcTSinit.o cpqfcTScontrol.o cpqfcTSi2c.o cpqfcTSworker.o cpqfcTStrigger.o
...
cpqfc.o: $(cpqfc-objs)
$(LD) -r -o $@ $(cpqfc-objs)
reply other threads:[~2001-08-08 13:24 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=2694.997277086@ocs3.ocs-net \
--to=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