From: James Bottomley <James.Bottomley@SteelEye.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
"Robert P. J. Day" <rpjday@mindspring.com>,
linux-scsi@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: some PCMCIA SCSI drivers can be built *only* as modules
Date: Mon, 26 Mar 2007 15:35:47 -0500 [thread overview]
Message-ID: <1174941347.3549.41.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <20070326200257.GA28622@infradead.org>
On Mon, 2007-03-26 at 21:02 +0100, Christoph Hellwig wrote:
> > > it would seem to make no sense that the "depends on" clause for this
> > > option includes "m", forcing this (and all other four entries in that
> > > Kconfig file, by the way) to be built as modules, while the help text
> > > for all five entries suggests you can select "y".
>
> In the old days pcmcia drivers had to be modular because pcmcia required
> a lot of userspace setup. It's not needed anymore these days and the
> dependencies can go.
I agree the non-legacy (CardBus and beyond) ones can be built in. I
thought the legacy 8 and 16 bit type I and II still had to be modular
because they still need setting up.
James
next prev parent reply other threads:[~2007-03-26 20:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0703250916090.22484@CPE00045a9c397f-CM001225dbafb6>
2007-03-26 13:27 ` some PCMCIA SCSI drivers can be built *only* as modules Stefan Richter
2007-03-26 20:02 ` Christoph Hellwig
2007-03-26 20:06 ` Robert P. J. Day
2007-03-26 20:31 ` Stefan Richter
2007-03-26 20:35 ` James Bottomley [this message]
2007-03-26 20:38 ` Christoph Hellwig
2007-03-26 21:06 ` James Bottomley
2007-03-30 20:48 ` Dominik Brodowski
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=1174941347.3549.41.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rpjday@mindspring.com \
--cc=stefanr@s5r6.in-berlin.de \
/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