Compiling SERIAL_JSM with PCI=n results in the following compile error:
<-- snip -->
...
LD .tmp_vmlinux1
drivers/built-in.o(.text+0x132800): In function `jsm_remove_one':
: undefined reference to `pci_release_regions'
make: *** [.tmp_vmlinux1] Error 1
<-- snip -->
Since this driver is only for PCi boards, this patch adds a dependency
on PCI.
Since I noticed that the Kconfig entry used whitespace instead of tabs,
I corrected this, too.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
--- linux-2.6.12-rc1-mm4-full/drivers/serial/Kconfig.old 2005-04-01
00:16:07.000000000 +0200
+++ linux-2.6.12-rc1-mm4-full/drivers/serial/Kconfig 2005-04-01
00:19:15.000000000 +0200
@@ -828,18 +828,19 @@
a console on a serial port, say Y. Otherwise, say N.
config SERIAL_JSM
- tristate "Digi International NEO PCI Support"
- select SERIAL_CORE
- help
- This is a driver for Digi International's Neo series
- of cards which provide multiple serial ports. You would need
- something like this to connect more than two modems to your Linux
- box, for instance in order to become a dial-in server. This driver
- supports PCI boards only.
- If you have a card like this, say Y here and read the file
- <file:Documentation/jsm.txt>.
+ tristate "Digi International NEO PCI Support"
+ depends on PCI
+ select SERIAL_CORE
+ help
+ This is a driver for Digi International's Neo series
+ of cards which provide multiple serial ports. You would need
+ something like this to connect more than two modems to your Linux
+ box, for instance in order to become a dial-in server. This driver
+ supports PCI boards only.
+ If you have a card like this, say Y here and read the file
+ <file:Documentation/jsm.txt>.
- To compile this driver as a module, choose M here: the
- module will be called jsm.
+ To compile this driver as a module, choose M here: the
+ module will be called jsm.
endmenu
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
