From: Rob Herring <robh@kernel.org>
To: Kejian Yan <yankejian@huawei.com>
Cc: davem@davemloft.net, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
catalin.marinas@arm.com, will.deacon@arm.com,
huangdaode@hisilicon.com, liguozhu@huawei.com, arnd@arndb.de,
fengguang.wu@intel.com, salil.mehta@huawei.com,
andriy.shevchenko@linux.intel.com, lisheng011@huawei.com,
haifeng.wei@huawei.com, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linuxarm@huawei.com
Subject: Re: [PATCH v2 next-next] net: hns: enet specifies a reference to dsaf
Date: Thu, 14 Jan 2016 20:28:00 -0600 [thread overview]
Message-ID: <20160115022800.GA29856@rob-hp-laptop> (raw)
In-Reply-To: <1452654880-28980-1-git-send-email-yankejian@huawei.com>
On Wed, Jan 13, 2016 at 11:14:40AM +0800, Kejian Yan wrote:
> This patch replace the assoication between dsaf and enet from string
> matching to object reference. It requires the DTS to be updated within
> BIOS. Thanks god it can be done for all released boards.
>
> Signed-off-by: Kejian Yan <yankejian@huawei.com>
> ---
> change log:
> v2:
> merge the two patches into one to allow bisection.
>
> v1:
> first submit.
>
> v1 patch reference:
> https://lkml.org/lkml/2015/12/5/11
> https://lkml.org/lkml/2015/12/5/12
> ---
> .../devicetree/bindings/net/hisilicon-hns-dsaf.txt | 5 +----
> .../devicetree/bindings/net/hisilicon-hns-nic.txt | 7 ++++---
> arch/arm64/boot/dts/hisilicon/hip05_hns.dtsi | 19 +++++++++----------
Acked-by: Rob Herring <robh@kernel.org>
> drivers/net/ethernet/hisilicon/hns/hnae.c | 17 +++++++----------
> drivers/net/ethernet/hisilicon/hns/hnae.h | 7 +++++--
> drivers/net/ethernet/hisilicon/hns/hns_ae_adapt.c | 4 ++++
> drivers/net/ethernet/hisilicon/hns/hns_dsaf_main.c | 10 +---------
> drivers/net/ethernet/hisilicon/hns/hns_dsaf_main.h | 1 +
> drivers/net/ethernet/hisilicon/hns/hns_enet.c | 13 +++++++++----
> drivers/net/ethernet/hisilicon/hns/hns_enet.h | 2 +-
> 10 files changed, 42 insertions(+), 43 deletions(-)
next prev parent reply other threads:[~2016-01-15 2:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 3:14 [PATCH v2 next-next] net: hns: enet specifies a reference to dsaf Kejian Yan
2016-01-14 3:00 ` Yisen Zhuang
2016-01-14 9:43 ` Andy Shevchenko
2016-01-18 11:35 ` Yankejian (Hackim Yim)
[not found] ` <569F2DEC.9040209@huawei.com>
2016-01-20 9:36 ` Andy Shevchenko
2016-01-20 11:10 ` Yankejian (Hackim Yim)
2016-01-15 2:28 ` Rob Herring [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-01-13 3:01 Kejian Yan
2016-01-13 2:52 ` Yankejian (Hackim Yim)
2016-01-13 2:54 ` David Miller
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=20160115022800.GA29856@rob-hp-laptop \
--to=robh@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=fengguang.wu@intel.com \
--cc=galak@codeaurora.org \
--cc=haifeng.wei@huawei.com \
--cc=huangdaode@hisilicon.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=liguozhu@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lisheng011@huawei.com \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=pawel.moll@arm.com \
--cc=salil.mehta@huawei.com \
--cc=will.deacon@arm.com \
--cc=yankejian@huawei.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