linux-amlogic.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Neil Armstrong <narmstrong@baylibre.com>
To: David Miller <davem@davemloft.net>
Cc: devicetree@vger.kernel.org, martin.blumenstingl@googlemail.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	robh+dt@kernel.org, linux-amlogic@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/2] dt-bindings: net: meson-dwmac: convert to yaml
Date: Fri, 9 Aug 2019 11:31:58 +0200	[thread overview]
Message-ID: <e39ca095-d68e-7231-f746-2470e16cd2e9@baylibre.com> (raw)
In-Reply-To: <20190808.112033.180369877501058953.davem@davemloft.net>

Hi,

On 08/08/2019 20:20, David Miller wrote:
> From: Neil Armstrong <narmstrong@baylibre.com>
> Date: Thu,  8 Aug 2019 13:40:59 +0200
> 
>> This patchsets converts the Amlogic Meson DWMAC glue bindings over to
>> YAML schemas using the already converted dwmac bindings.
>>
>> The first patch is needed because the Amlogic glue needs a supplementary
>> reg cell to access the DWMAC glue registers.
>>
>> Changes since v2:
>> - Added review tags
>> - Updated allwinner,sun7i-a20-gmac.yaml reg maxItems
> 
> Where is this targetted to be merged, an ARM tree?  Or one of my
> networking trees?
> 

I assume you can take it in one of your net trees.

Thanks,
Neil

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

      reply	other threads:[~2019-08-09  9:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-08 11:40 [PATCH v3 0/2] dt-bindings: net: meson-dwmac: convert to yaml Neil Armstrong
2019-08-08 11:41 ` [PATCH v3 1/2] dt-bindings: net: snps, dwmac: update reg minItems maxItems Neil Armstrong
2019-08-08 11:41 ` [PATCH v3 2/2] dt-bindings: net: meson-dwmac: convert to yaml Neil Armstrong
2019-08-08 18:20 ` [PATCH v3 0/2] " David Miller
2019-08-09  9:31   ` Neil Armstrong [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=e39ca095-d68e-7231-f746-2470e16cd2e9@baylibre.com \
    --to=narmstrong@baylibre.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=netdev@vger.kernel.org \
    --cc=robh+dt@kernel.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).