From: David Miller <davem@davemloft.net>
To: yasu.isimatu@gmail.com
Cc: netdev@vger.kernel.org, izumi.taku@jp.fujitsu.com
Subject: Re: [PATCH v3 0/2] fjes: Do not load fjes driver
Date: Wed, 22 Mar 2017 12:39:04 -0700 (PDT) [thread overview]
Message-ID: <20170322.123904.2127246481524648740.davem@davemloft.net> (raw)
In-Reply-To: <c0bb31ae-1f5b-9b73-ed51-a8d56361ff59@gmail.com>
From: YASUAKI ISHIMATSU <yasu.isimatu@gmail.com>
Date: Tue, 21 Mar 2017 11:28:02 -0400
> 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
Series applied, thanks.
next prev parent reply other threads:[~2017-03-22 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 15:28 [PATCH v3 0/2] fjes: Do not load fjes driver YASUAKI ISHIMATSU
2017-03-21 15:44 ` [PATCH v3 1/2] fjes: Do not load fjes driver if system does not have extended socket device YASUAKI ISHIMATSU
2017-03-21 15:46 ` [PATCH v3 2/2] fjes: Do not load fjes driver if extended socket device is not power on YASUAKI ISHIMATSU
2017-03-22 19:39 ` David Miller [this message]
2017-03-23 0:02 ` [PATCH v3 0/2] fjes: Do not load fjes driver Izumi, Taku
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=20170322.123904.2127246481524648740.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).