diff options
| author | Stephen Hemminger <shemminger@vyatta.com> | 2008-10-22 01:04:27 (GMT) |
|---|---|---|
| committer | Jeff Garzik <jgarzik@redhat.com> | 2008-10-22 11:00:28 (GMT) |
| commit | de4549cae088a74262834178b71fb25dbec2c376 (patch) | |
| tree | c2d94c2648ac6e4d3c152ab0137289a4d84ac981 /drivers/net/8139too.c | |
| parent | 421e02f0e9c3335028750ee411e5534dab82efbd (diff) | |
| download | linux-de4549cae088a74262834178b71fb25dbec2c376.tar.xz | |
8139x: reduce message severity on driver overlap
The 8139 drivers are a source of error messages that confuse users.
Since this device can not be disambiguated by normal PCI device
id's two drivers match the same info. But the module utilities
seem to correctly handle this overlap, they try one driver, then
if that doesn't load try the other. Therefore there is no need for
a message to be logged with error level severity, just using info
level instead. Can't be completely silent because user might have
configure one driver and forgot the other one.
Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
Signed-off-by: Jeff Garzik <jgarzik@redhat.com>
Diffstat (limited to 'drivers/net/8139too.c')
| -rw-r--r-- | drivers/net/8139too.c | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/drivers/net/8139too.c b/drivers/net/8139too.c index 0daf8c1..63f906b 100644 --- a/drivers/net/8139too.c +++ b/drivers/net/8139too.c @@ -946,10 +946,9 @@ static int __devinit rtl8139_init_one (struct pci_dev *pdev, if (pdev->vendor == PCI_VENDOR_ID_REALTEK && pdev->device == PCI_DEVICE_ID_REALTEK_8139 && pdev->revision >= 0x20) { dev_info(&pdev->dev, - "This (id %04x:%04x rev %02x) is an enhanced 8139C+ chip\n", + "This (id %04x:%04x rev %02x) is an enhanced 8139C+ chip, use 8139cp\n", pdev->vendor, pdev->device, pdev->revision); - dev_info(&pdev->dev, - "Use the \"8139cp\" driver for improved performance and stability.\n"); + return -ENODEV; } if (pdev->vendor == PCI_VENDOR_ID_REALTEK && |