From: Markus Lidel <Markus.Lidel@shadowconnect.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 5/5] I2O subsystem fixing and cleanup for 2.6 - i2o-makefile-cleanup.patch
Date: Thu, 29 Apr 2004 22:31:38 +0200 [thread overview]
Message-ID: <4091662A.5040907@shadowconnect.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 0 bytes --]
[-- Attachment #2: i2o-makefile-cleanup.patch --]
[-- Type: text/plain, Size: 1755 bytes --]
--- a/drivers/message/i2o/Kconfig 2004-04-04 05:36:15.000000000 +0200
+++ b/drivers/message/i2o/Kconfig 2004-04-27 10:05:52.000000000 +0200
@@ -3,7 +3,7 @@
config I2O
tristate "I2O support"
- depends on PCI && !64BIT
+ depends on PCI
---help---
The Intelligent Input/Output (I2O) architecture allows hardware
drivers to be split into two parts: an operating system specific
@@ -20,19 +20,20 @@
drivers and OSM's with the following questions.
To compile this support as a module, choose M here: the
- modules will be called i2o_core and i2o_config.
+ modules will be called i2o_core.
If unsure, say N.
-config I2O_PCI
- tristate "I2O PCI support"
+config I2O_CONFIG
+ tristate "I2O Configuration support"
depends on PCI && I2O
help
- Say Y for support of PCI bus I2O interface adapters. Currently this
- is the only variety supported, so you should say Y.
+ Say Y for support of the configuration interface for the I2O adapters.
+ If you have a RAID controller from Adaptec and you want to use the
+ raidutils to manage your RAID array, you have to say Y here.
To compile this support as a module, choose M here: the
- module will be called i2o_pci.
+ module will be called i2o_config.
config I2O_BLOCK
tristate "I2O Block OSM"
--- a/drivers/message/i2o/Makefile 2004-04-04 05:37:37.000000000 +0200
+++ b/drivers/message/i2o/Makefile 2004-04-27 10:06:09.000000000 +0200
@@ -5,7 +5,8 @@
# In the future, some of these should be built conditionally.
#
-obj-$(CONFIG_I2O) += i2o_core.o i2o_config.o
+obj-$(CONFIG_I2O) += i2o_core.o
+obj-$(CONFIG_I2O_CONFIG)+= i2o_config.o
obj-$(CONFIG_I2O_BLOCK) += i2o_block.o
obj-$(CONFIG_I2O_SCSI) += i2o_scsi.o
obj-$(CONFIG_I2O_PROC) += i2o_proc.o
reply other threads:[~2004-04-29 20:30 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=4091662A.5040907@shadowconnect.com \
--to=markus.lidel@shadowconnect.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