From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND v2 net-next] net: hisilicon: updates HNS config and documents
Date: Fri, 30 Oct 2015 15:20:18 +0100 [thread overview]
Message-ID: <4549013.K7sn8Pca5b@wuerfel> (raw)
In-Reply-To: <1445944594-244149-1-git-send-email-huangdaode@hisilicon.com>
On Tuesday 27 October 2015 19:16:34 huangdaode wrote:
> mdio at 803c0000 {
> #address-cells = <1>;
> #size-cells = <0>;
> - compatible = "hisilicon,mdio","hisilicon,hns-mdio";
> + compatible = "hisilicon,hns-mdio","hisilicon,mdio";
> reg = <0x0 0x803c0000 0x0 0x10000>;
>
>
Does "hisilicon,mdio" actually have a specific meaning? Is that just there
for legacy reasons?
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: huangdaode <huangdaode@hisilicon.com>
Cc: davem@davemloft.net, robh+dt@kernel.org, pawel.moll@arm.com,
mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
galak@codeaurora.org, catalin.marinas@arm.com,
will.deacon@arm.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, liguozhu@hisilicon.com,
Yisen.Zhuang@huawei.com, netdev@vger.kernel.org,
linuxarm@huawei.com, salil.mehta@huawei.com,
kenneth-lee-2012@foxmail.com, xuwei5@hisilicon.com,
lisheng011@huawei.com, lipeng321@huawei.com
Subject: Re: [PATCH RESEND v2 net-next] net: hisilicon: updates HNS config and documents
Date: Fri, 30 Oct 2015 15:20:18 +0100 [thread overview]
Message-ID: <4549013.K7sn8Pca5b@wuerfel> (raw)
In-Reply-To: <1445944594-244149-1-git-send-email-huangdaode@hisilicon.com>
On Tuesday 27 October 2015 19:16:34 huangdaode wrote:
> mdio@803c0000 {
> #address-cells = <1>;
> #size-cells = <0>;
> - compatible = "hisilicon,mdio","hisilicon,hns-mdio";
> + compatible = "hisilicon,hns-mdio","hisilicon,mdio";
> reg = <0x0 0x803c0000 0x0 0x10000>;
>
>
Does "hisilicon,mdio" actually have a specific meaning? Is that just there
for legacy reasons?
Arnd
next prev parent reply other threads:[~2015-10-30 14:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 11:16 [PATCH RESEND v2 net-next] net: hisilicon: updates HNS config and documents huangdaode
2015-10-27 11:16 ` huangdaode
2015-10-27 11:16 ` huangdaode
2015-10-27 11:16 ` huangdaode
2015-10-28 3:20 ` David Miller
2015-10-28 3:20 ` David Miller
2015-10-30 14:20 ` Arnd Bergmann [this message]
2015-10-30 14:20 ` Arnd Bergmann
2015-10-31 1:40 ` huangdaode
2015-10-31 1:40 ` huangdaode
2015-10-31 1:40 ` huangdaode
2015-10-31 1:40 ` huangdaode
2015-10-31 2:18 ` Salil Mehta
2015-10-31 2:18 ` Salil Mehta
2015-10-31 2:18 ` Salil Mehta
2015-10-31 2:18 ` Salil Mehta
2015-11-02 22:05 ` Arnd Bergmann
2015-11-02 22:05 ` Arnd Bergmann
2015-11-12 2:11 ` huangdaode
2015-11-12 2:11 ` huangdaode
2015-11-12 2:11 ` huangdaode
2015-11-12 2:11 ` huangdaode
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=4549013.K7sn8Pca5b@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.