diff options
author | Markus Lidel <Markus.Lidel@shadowconnect.com> | 2005-06-24 01:02:23 -0400 |
---|---|---|
committer | Linus Torvalds <torvalds@ppc970.osdl.org> | 2005-06-24 03:05:29 -0400 |
commit | f33213ecf49c98da4e85121b592c3bea8057c2e6 (patch) | |
tree | da7e51e7204625f21371eac23a931f4fe479e9db /drivers/message/i2o/Kconfig | |
parent | 9e87545f06930c1d294423a8091d1077e7444a47 (diff) |
[PATCH] I2O: Lindent run and replacement of printk through osm printing functions
Lindent run and replaced printk() through the corresponding osm_*() function
Signed-off-by: Markus Lidel <Markus.Lidel@shadowconnect.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'drivers/message/i2o/Kconfig')
-rw-r--r-- | drivers/message/i2o/Kconfig | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/drivers/message/i2o/Kconfig b/drivers/message/i2o/Kconfig index 94b6d676c5cb..06e8eb19a05c 100644 --- a/drivers/message/i2o/Kconfig +++ b/drivers/message/i2o/Kconfig | |||
@@ -44,8 +44,8 @@ config I2O_EXT_ADAPTEC_DMA64 | |||
44 | 44 | ||
45 | config I2O_CONFIG | 45 | config I2O_CONFIG |
46 | tristate "I2O Configuration support" | 46 | tristate "I2O Configuration support" |
47 | depends on PCI && I2O | 47 | depends on I2O |
48 | help | 48 | ---help--- |
49 | Say Y for support of the configuration interface for the I2O adapters. | 49 | Say Y for support of the configuration interface for the I2O adapters. |
50 | If you have a RAID controller from Adaptec and you want to use the | 50 | If you have a RAID controller from Adaptec and you want to use the |
51 | raidutils to manage your RAID array, you have to say Y here. | 51 | raidutils to manage your RAID array, you have to say Y here. |
@@ -74,7 +74,7 @@ config I2O_BUS | |||
74 | config I2O_BLOCK | 74 | config I2O_BLOCK |
75 | tristate "I2O Block OSM" | 75 | tristate "I2O Block OSM" |
76 | depends on I2O | 76 | depends on I2O |
77 | help | 77 | ---help--- |
78 | Include support for the I2O Block OSM. The Block OSM presents disk | 78 | Include support for the I2O Block OSM. The Block OSM presents disk |
79 | and other structured block devices to the operating system. If you | 79 | and other structured block devices to the operating system. If you |
80 | are using an RAID controller, you could access the array only by | 80 | are using an RAID controller, you could access the array only by |
@@ -87,7 +87,7 @@ config I2O_BLOCK | |||
87 | config I2O_SCSI | 87 | config I2O_SCSI |
88 | tristate "I2O SCSI OSM" | 88 | tristate "I2O SCSI OSM" |
89 | depends on I2O && SCSI | 89 | depends on I2O && SCSI |
90 | help | 90 | ---help--- |
91 | Allows direct SCSI access to SCSI devices on a SCSI or FibreChannel | 91 | Allows direct SCSI access to SCSI devices on a SCSI or FibreChannel |
92 | I2O controller. You can use both the SCSI and Block OSM together if | 92 | I2O controller. You can use both the SCSI and Block OSM together if |
93 | you wish. To access a RAID array, you must use the Block OSM driver. | 93 | you wish. To access a RAID array, you must use the Block OSM driver. |
@@ -99,7 +99,7 @@ config I2O_SCSI | |||
99 | config I2O_PROC | 99 | config I2O_PROC |
100 | tristate "I2O /proc support" | 100 | tristate "I2O /proc support" |
101 | depends on I2O | 101 | depends on I2O |
102 | help | 102 | ---help--- |
103 | If you say Y here and to "/proc file system support", you will be | 103 | If you say Y here and to "/proc file system support", you will be |
104 | able to read I2O related information from the virtual directory | 104 | able to read I2O related information from the virtual directory |
105 | /proc/i2o. | 105 | /proc/i2o. |