From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: randy.dunlap@oracle.com
Cc: akpm@osdl.org, mm-commits@vger.kernel.org,
James.Bottomley@steeleye.com, zippel@linux-m68k.org,
linux-kernel@vger.kernel.org
Subject: Re: + revert-iscsi-build-failure-use-depends-instead-of.patch added to -mm tree
Date: Thu, 02 Nov 2006 11:54:56 +0100 [thread overview]
Message-ID: <4549CE80.5080307@s5r6.in-berlin.de> (raw)
In-Reply-To: <200611020640.kA26edl0003496@shell0.pdx.osdl.net>
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> Remove all (2) "select NET" instances from all kernel Kconfig files. Use
> "depends on" for them instead. As Roman Zippel commented, "please don't
> select NET, it's way too broad."
>
> This affects all IEEE1394 drivers and some SCSI drivers. Networking (NET)
> will have to be enabled before any IEEE1394 or a few SCSI drivers can be
> enabled. In particular for SCSI, the QLogic ISP4xxx driver
> (SCSI_QLA_ISCSI) and any FiberChannel drivers are affected.
>
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> Cc: James Bottomley <James.Bottomley@steeleye.com>
> Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>
> Cc: Roman Zippel <zippel@linux-m68k.org>
> Signed-off-by: Andrew Morton <akpm@osdl.org>
> ---
>
> drivers/ieee1394/Kconfig | 5 ++++-
> drivers/scsi/Kconfig | 13 +++++++++----
> drivers/scsi/qla4xxx/Kconfig | 8 ++++----
> 3 files changed, 17 insertions(+), 9 deletions(-)
[...]
I'm OK with that change. You could have submitted the IEEE 1394 part
separately though.
A comment on the patch description: Only the eth1394 driver and the
ieee1394 core driver depend directly on NET. (All other FireWire drivers
depend on ieee1394 of course.) ieee1394's dependency on NET is planned
to be removed by a minor change to its implementation but we don't have
a deadline for this, as usual...
--
Stefan Richter
-=====-=-==- =-== ---=-
http://arcgraph.de/sr/
parent reply other threads:[~2006-11-02 10:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200611020640.kA26edl0003496@shell0.pdx.osdl.net>]
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=4549CE80.5080307@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®