From: Paolo Abeni <pabeni@redhat.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Kunihiko Hayashi <hayashi.kunihiko@socionext.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>
Subject: Re: [PATCH 0/2] dt-bindings: net: Fix ave descriptions
Date: Thu, 07 Apr 2022 10:18:29 +0200 [thread overview]
Message-ID: <62711467c3990d38ed8a11bf1c7c2594e8e1b436.camel@redhat.com> (raw)
In-Reply-To: <1649145181-30001-1-git-send-email-hayashi.kunihiko@socionext.com>
Hi,
On Tue, 2022-04-05 at 16:52 +0900, Kunihiko Hayashi wrote:
> This series fixes dt-schema descriptions for ave4 controller.
>
> Kunihiko Hayashi (2):
> dt-bindings: net: ave: Clean up clocks, resets, and their names using
> compatible string
> dt-bindings: net: ave: Use unevaluatedProperties
>
> .../bindings/net/socionext,uniphier-ave4.yaml | 57 +++++++++++++------
> 1 file changed, 39 insertions(+), 18 deletions(-)
@Rob: since you acked this series, I guess you prefer/except this will
go via net net-next tree, is that correct?
Thanks!
Paolo
next prev parent reply other threads:[~2022-04-07 8:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 7:52 [PATCH 0/2] dt-bindings: net: Fix ave descriptions Kunihiko Hayashi
2022-04-05 7:53 ` [PATCH 1/2] dt-bindings: net: ave: Clean up clocks, resets, and their names using compatible string Kunihiko Hayashi
2022-04-06 18:16 ` Rob Herring
2022-04-05 7:53 ` [PATCH 2/2] dt-bindings: net: ave: Use unevaluatedProperties Kunihiko Hayashi
2022-04-06 18:16 ` Rob Herring
2022-04-07 8:18 ` Paolo Abeni [this message]
2022-04-07 13:59 ` [PATCH 0/2] dt-bindings: net: Fix ave descriptions Rob Herring
2022-04-08 11:00 ` patchwork-bot+netdevbpf
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=62711467c3990d38ed8a11bf1c7c2594e8e1b436.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--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).