From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: David Miller <davem@davemloft.net>
Cc: robh+dt@kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, mark.rutland@arm.com,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] DT: net: renesas,ravb: document R8A77980 bindings
Date: Sun, 25 Feb 2018 11:48:31 +0300 [thread overview]
Message-ID: <92bde878-2de5-a56f-8074-c1b1313a8c23@cogentembedded.com> (raw)
In-Reply-To: <20180224.215317.982381501908572398.davem@davemloft.net>
Hello!
On 2/25/2018 5:53 AM, David Miller wrote:
>>> Renesas R-Car V3H (R8A77980) SoC has the R-Car gen3 compatible EtherAVB >>> device, so document the SoC specific bindings.>>>>>> Signed-off-by:
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>>>>>>> --->>> The patch is
against DaveM's 'net-next.git' repo but I wouldn't mind if it's>>> applied to
'net.git' instead. :-)>>>> David, I see this patch was marked as "not
applicable" in patchwork. Why, because>> it was posted during the merge
window?> > No because I thought the relevant architecture tree would take a
mere> DT update.
Well, so far the binding updates have been merged via the appropriate
driver subsystem trees, look at e.g. this patch:
https://patchwork.ozlabs.org/patch/813037/
MBR, Sergei
next prev parent reply other threads:[~2018-02-25 8:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 20:13 [PATCH] DT: net: renesas,ravb: document R8A77980 bindings Sergei Shtylyov
2018-02-01 20:27 ` Geert Uytterhoeven
[not found] ` <CAMuHMdWeN8hf3rxHRofn9rD3MKD4rcPVVNM3W3+7nBatmUvxjw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-02-02 8:57 ` Simon Horman
2018-02-05 6:09 ` Rob Herring
2018-02-24 18:01 ` Sergei Shtylyov
2018-02-25 2:53 ` David Miller
2018-02-25 8:48 ` Sergei Shtylyov [this message]
2018-02-25 15:03 ` Sergei Shtylyov
2018-02-26 10:58 ` Simon Horman
2018-02-26 20:10 ` David Miller
2018-02-27 8:28 ` Simon Horman
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=92bde878-2de5-a56f-8074-c1b1313a8c23@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.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).