From: David Miller <davem@davemloft.net>
To: yasu.isimatu@gmail.com
Cc: netdev@vger.kernel.org, izumi.taku@jp.fujitsu.com
Subject: Re: [PATCH v2] fjes: Do not load fjes driver if system does not have extended socket device.
Date: Thu, 09 Mar 2017 17:35:19 -0800 (PST) [thread overview]
Message-ID: <20170309.173519.1406243244628930968.davem@davemloft.net> (raw)
In-Reply-To: <7a1a2dbc-99e0-06ba-2261-6e6382937486@gmail.com>
From: Yasuaki Ishimatsu <yasu.isimatu@gmail.com>
Date: Wed, 8 Mar 2017 16:05:18 -0500
> 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 a check that the server
> has a extended socket device or not.
>
> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
> CC: Taku Izumi <izumi.taku@jp.fujitsu.com>
> ---
> v2:
> - Order local variable declarations from longest to shortest line
This patch does not apply cleanly to the net tree.
next prev parent reply other threads:[~2017-03-10 1:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 21:05 [PATCH v2] fjes: Do not load fjes driver if system does not have extended socket device Yasuaki Ishimatsu
2017-03-10 1:35 ` David Miller [this message]
2017-03-10 17:09 ` Yasuaki Ishimatsu
2017-03-13 1:02 ` Izumi, Taku
2017-03-14 16:07 ` YASUAKI ISHIMATSU
2017-03-12 18:29 ` Bjørn Mork
2017-03-14 14:47 ` YASUAKI ISHIMATSU
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170309.173519.1406243244628930968.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=izumi.taku@jp.fujitsu.com \
--cc=netdev@vger.kernel.org \
--cc=yasu.isimatu@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).