From: "Izumi, Taku" <izumi.taku@jp.fujitsu.com>
To: Gabriele Paoloni <gabriele.paoloni@huawei.com>
Cc: Linuxarm <linuxarm@huawei.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"liudongdong (C)" <liudongdong3@huawei.com>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: RE: [bug discuss] fjes driver call trace warning, "PNP0C02" used in fjes seems like a bug,
Date: Thu, 9 Jun 2016 08:48:45 +0000 [thread overview]
Message-ID: <E86EADE93E2D054CBCD4E708C38D364A7379ED59@G01JPEXMBYT01> (raw)
In-Reply-To: <EE11001F9E5DDD47B7634E2F8A612F2E1F7783A9@lhreml507-mbx>
Dear Gao,
> From a SW perspective it like an acpi driver that uses "PNP0C02"
> as driver ids to perform the driver match in the ACPI table.
>
> From my understanding this is wrong in principle because that identifier
> must be used to reserve motherboard resources (see par 4.1.2 of the PCI
> Firmware Specifications v3.2)
>
> Therefore such identifier it is used from
> http://lxr.free-electrons.com/source/drivers/pnp/system.c
> to reserve such resources.
>
> Basically your driver is breaking any other device that
> needs to reserve motherboard resources through system.c
> driver.
>
> @David Miller, what is your opinion about this?
> I think this driver should be reverted...
I'm willing to revise my driver if it's something wrong.
I can't reproduce this problem. Could you please show me how to reproduce problem ?
Sincerely,
Taku Izumi
prev parent reply other threads:[~2016-06-09 8:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <57515004.1080301@huawei.com>
[not found] ` <EE11001F9E5DDD47B7634E2F8A612F2E1F76DB68@lhreml507-mbx>
[not found] ` <E86EADE93E2D054CBCD4E708C38D364A7379C541@G01JPEXMBYT01>
[not found] ` <EE11001F9E5DDD47B7634E2F8A612F2E1F7715BA@lhreml507-mbx>
[not found] ` <E86EADE93E2D054CBCD4E708C38D364A7379DCD7@G01JPEXMBYT01>
2016-06-08 7:10 ` Gabriele Paoloni
2016-06-09 8:48 ` Izumi, Taku [this message]
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=E86EADE93E2D054CBCD4E708C38D364A7379ED59@G01JPEXMBYT01 \
--to=izumi.taku@jp.fujitsu.com \
--cc=davem@davemloft.net \
--cc=gabriele.paoloni@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=liudongdong3@huawei.com \
--cc=netdev@vger.kernel.org \
--subject='RE: [bug discuss] fjes driver call trace warning, "PNP0C02" used in fjes seems like a bug,' \
/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
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).