[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <E86EADE93E2D054CBCD4E708C38D364A741D2417@G01JPEXMBYT21>
Date: Thu, 23 Mar 2017 00:02:00 +0000
From: "Izumi, Taku" <izumi.taku@...fujitsu.com>
To: 'YASUAKI ISHIMATSU' <yasu.isimatu@...il.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
CC: David Miller <davem@...emloft.net>
Subject: RE: [PATCH v3 0/2] fjes: Do not load fjes driver
Tested-by: Taku Izumi <izumi.taku@...fujitsu.com>
> -----Original Message-----
> From: YASUAKI ISHIMATSU [mailto:yasu.isimatu@...il.com]
> Sent: Wednesday, March 22, 2017 12:28 AM
> To: netdev@...r.kernel.org
> Cc: David Miller <davem@...emloft.net>; Izumi, Taku/泉 拓
> <izumi.taku@...fujitsu.com>; yasu.isimatu@...il.com
> Subject: [PATCH v3 0/2] fjes: Do not load fjes driver
>
> The fjes driver is used only by FUJITSU servers and almost of all servers
> in the world never use it. But currently if ACPI PNP0C02 is defined in the
> ACPI table, the following message is always shown:
>
> "FUJITSU Extended Socket Network Device Driver - version 1.2
> - Copyright (c) 2015 FUJITSU LIMITED"
>
> The message makes users confused because there is no reason that the message
> is shown in other vendor servers.
>
> To avoid the confusion, the patch adds several checks.
>
> v3:
> - Rebase on latest net tree.
> - Add _STA method check to avoid loading fjes driver.
>
> v2:
> - Order local variable declarations from longest to shortest line
>
> Yasuaki Ishimatsu(2):
> fjes: Do not load fjes driver if system does not have extended socket
> device.
> fjes: Do not load fjes driver if extended socket device is not power on.
>
> drivers/net/fjes/fjes_main.c | 76
> +++++++++++++++++++++++++++++++++++++++++---
> 1 file changed, 71 insertions(+), 5 deletions(-)
Powered by blists - more mailing lists