From: Sam Ravnborg <sam@ravnborg.org>
To: Alan Cox <alan@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.5.44-ac5
Date: Mon, 28 Oct 2002 19:18:58 +0100 [thread overview]
Message-ID: <20021028181858.GA1245@mars.ravnborg.org> (raw)
In-Reply-To: <200210281452.g9SEqwF17910@devserv.devel.redhat.com>
On Mon, Oct 28, 2002 at 09:52:58AM -0500, Alan Cox wrote:
> o Work around makefile breakages for pcmcia scsi (me)
> | Will whoever broke vpath please fix it properly
Being "partner in crime" I would like to give it a try.
Could you give an advice what is the best approach?
What I have thought of so far:
1) Create a small qlogic_fas_stub.c in the pcmia subdirectory that
includes the qlogic_fas.c source in the scsi directory.
2) Do some magic in the makefile so I have a .o file present in
the pcmia sub-directory, build based on the src in the scsi directory.
I never did any of the above because of the following reasons:
a) I have not seen 1) used before, and generally does not like
including .c files in .c files.
b) Solution 2) looked too ugly to me.
The only difference between the PCMIA version and the normal one is
small details with respect to interrupts.
I wonder if that could be configured during startup of the driver, hereby
selecting between normal or PCMIA version.
But i have never written a Linux driver so my knowledge in this area is
too low to judge.
Sam
next prev parent reply other threads:[~2002-10-28 18:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-28 14:52 Linux 2.5.44-ac5 Alan Cox
2002-10-28 18:18 ` Sam Ravnborg [this message]
2002-10-28 18:55 ` Alan Cox
2002-10-28 22:13 ` Bill Davidsen
2002-10-28 22:46 ` conflicting types for sys_swap{on,off} " Tom Vier
2002-10-28 22:55 ` Thorsten Kranzkowski
2002-10-28 23:56 ` ipt_do_table unaligned traps " Tom Vier
2002-10-29 10:00 ` Adrian Bunk
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=20021028181858.GA1245@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=alan@redhat.com \
--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