public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: yankejian@huawei.com (Kejian Yan)
To: linux-arm-kernel@lists.infradead.org
Subject: [patch v3 net-next 0/2] dts: hisi: fixes no syscon fault when init mdio
Date: Wed, 13 Jan 2016 15:09:57 +0800	[thread overview]
Message-ID: <1452668999-443-1-git-send-email-yankejian@huawei.com> (raw)

This patchset fixes the bug that eth can't initial successful on hip05-D02
because the dts files doesn't match the source code.

Kejian Yan (2):
  dts: hisi: fixes no syscon fault when init mdio
  net: hns: fixes no syscon error when init mdio
---
change log:
v3:
 1) uses capital letter at the beginning of sentences
 2) updates the right device node name

v2:
 1) update the related documented in the binding as well
 2) use the normal naming conventions using '-' instead of '_', and
    update the related *.c files.
v1:
 first submit

 .../devicetree/bindings/arm/hisilicon/hisilicon.txt      | 16 ++++++++++++++++
 arch/arm64/boot/dts/hisilicon/hip05.dtsi                 |  5 +++++
 arch/arm64/boot/dts/hisilicon/hip05_hns.dtsi             |  4 ++--
 drivers/net/ethernet/hisilicon/hns_mdio.c                |  2 +-
 4 files changed, 24 insertions(+), 3 deletions(-)

-- 
2.4.1

             reply	other threads:[~2016-01-13  7:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-13  7:09 Kejian Yan [this message]
2016-01-13  7:09 ` [patch v3 net-next 1/2] dts: hisi: fixes no syscon fault when init mdio Kejian Yan
2016-01-15  2:17   ` Rob Herring
2016-01-13  7:09 ` [patch v3 net-next 2/2] net: hns: fixes no syscon error " Kejian Yan
2016-01-15 19:40 ` [patch v3 net-next 0/2] dts: hisi: fixes no syscon fault " David Miller
  -- strict thread matches above, loose matches on Subject: below --
2016-01-13  3:01 [PATCH v2 next-next] net: hns: enet specifies a reference to dsaf Kejian Yan
2016-01-13  3:01 ` [patch v3 net-next 0/2] dts: hisi: fixes no syscon fault when init mdio Kejian Yan

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=1452668999-443-1-git-send-email-yankejian@huawei.com \
    --to=yankejian@huawei.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox