As I understand it, driver mrst_max3110 is only useful on Moorestown systems, so it should depend on X86_MRST. Signed-off-by: Jean Delvare <jdelvare@xxxxxxx> Cc: Alan Cox <alan@xxxxxxxxxxxxxxx> --- There are a few other drivers in a similar situation (i2c/busses/i2c-intel-mid, gpio/langwell_gpio, tty/serial/mfd, staging/sep) for which I suspect the same should be done, assuming that X86_MRST is for both Moorestown and Medfield. drivers/tty/serial/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- linux-3.1-rc4.orig/drivers/tty/serial/Kconfig 2011-08-16 11:49:57.000000000 +0200 +++ linux-3.1-rc4/drivers/tty/serial/Kconfig 2011-09-16 22:03:32.000000000 +0200 @@ -695,7 +695,7 @@ config SERIAL_SA1100_CONSOLE config SERIAL_MRST_MAX3110 tristate "SPI UART driver for Max3110" - depends on SPI_DW_PCI + depends on X86_MRST && SPI_DW_PCI select SERIAL_CORE select SERIAL_CORE_CONSOLE help -- Jean Delvare Suse L3 -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
