linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: matthias.bgg@gmail.com (Matthias Brugger)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] fixed ethernet binding violation for reset signal
Date: Thu, 20 Jul 2017 13:01:24 +0200	[thread overview]
Message-ID: <29c1debd-e7ac-9858-6969-cff37ae1d06f@gmail.com> (raw)
In-Reply-To: <1500520073.25149.2.camel@mtkswgap22>



On 07/20/2017 05:07 AM, Sean Wang wrote:
> Hi, Matthias
> 
> just a gentle ping on this
> 

Pushed now to v4.13-next/dts32

Thanks!

> 	Sean
> 
> 
> On Wed, 2017-06-21 at 15:49 +0800, sean.wang at mediatek.com wrote:
>> From: Sean Wang <sean.wang@mediatek.com>
>>
>> Fixed binding violation and also updated related binding documentation to
>> reflect the reset signals the MediaTek Ethernet requires.
>>
>> Sean Wang (2):
>>    dt-bindings: net: mediatek: update documentation for reset signals
>>    arm: dts: mt7623: fixup binding violation missing reset in ethernet
>>      node
>>
>>   Documentation/devicetree/bindings/net/mediatek-net.txt | 6 ++++--
>>   arch/arm/boot/dts/mt7623.dtsi                          | 4 ++++
>>   2 files changed, 8 insertions(+), 2 deletions(-)
>>
> 
> 

      reply	other threads:[~2017-07-20 11:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-21  7:49 [PATCH 0/2] fixed ethernet binding violation for reset signal sean.wang at mediatek.com
2017-06-21  7:49 ` [PATCH 1/2] dt-bindings: net: mediatek: update documentation for reset signals sean.wang at mediatek.com
2017-06-26 14:51   ` Rob Herring
2017-06-21  7:49 ` [PATCH 2/2] arm: dts: mt7623: fixup binding violation missing reset in ethernet node sean.wang at mediatek.com
2017-07-20  3:07 ` [PATCH 0/2] fixed ethernet binding violation for reset signal Sean Wang
2017-07-20 11:01   ` Matthias Brugger [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=29c1debd-e7ac-9858-6969-cff37ae1d06f@gmail.com \
    --to=matthias.bgg@gmail.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;
as well as URLs for NNTP newsgroup(s).