From: "Rob Herring (Arm)" <robh@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: linux-renesas-soc@vger.kernel.org,
Conor Dooley <conor+dt@kernel.org>, Felix Fietkau <nbd@nbd.name>,
"David S. Miller" <davem@davemloft.net>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Magnus Damm <magnus.damm@gmail.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Lorenzo Bianconi <lorenzo@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Eric Dumazet <edumazet@google.com>,
Sergei Shtylyov <sergei.shtylyov@gmail.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Kunihiko Hayashi <hayashi.kunihiko@socionext.com>,
Paolo Abeni <pabeni@redhat.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, Masami Hiramatsu <mhiramat@kernel.org>,
Sergey Shtylyov <s.shtylyov@omp.ru>,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH net-next 1/4] dt-bindings: net: mediatek,net: narrow interrupts per variants
Date: Mon, 19 Aug 2024 11:15:05 -0600 [thread overview]
Message-ID: <172408770465.1699134.17451371912936634019.robh@kernel.org> (raw)
In-Reply-To: <20240818172905.121829-1-krzysztof.kozlowski@linaro.org>
On Sun, 18 Aug 2024 19:29:02 +0200, Krzysztof Kozlowski wrote:
> Each variable-length property like interrupts must have fixed
> constraints on number of items for given variant in binding. The
> clauses in "if:then:" block should define both limits: upper and lower.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
> Documentation/devicetree/bindings/net/mediatek,net.yaml | 3 +++
> 1 file changed, 3 insertions(+)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2024-08-19 17:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-18 17:29 [PATCH net-next 1/4] dt-bindings: net: mediatek,net: narrow interrupts per variants Krzysztof Kozlowski
2024-08-18 17:29 ` [PATCH net-next 2/4] dt-bindings: net: mediatek,net: add top-level constraints Krzysztof Kozlowski
2024-08-19 17:15 ` Rob Herring (Arm)
2024-08-18 17:29 ` [PATCH net-next 3/4] dt-bindings: net: renesas,etheravb: " Krzysztof Kozlowski
2024-08-19 17:15 ` Rob Herring (Arm)
2024-08-18 17:29 ` [PATCH net-next 4/4] dt-bindings: net: socionext,uniphier-ave4: " Krzysztof Kozlowski
2024-08-19 17:15 ` Rob Herring (Arm)
2024-08-19 17:15 ` Rob Herring (Arm) [this message]
2024-08-20 22:40 ` [PATCH net-next 1/4] dt-bindings: net: mediatek,net: narrow interrupts per variants 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=172408770465.1699134.17451371912936634019.robh@kernel.org \
--to=robh@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=geert+renesas@glider.be \
--cc=hayashi.kunihiko@socionext.com \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=magnus.damm@gmail.com \
--cc=matthias.bgg@gmail.com \
--cc=mhiramat@kernel.org \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=s.shtylyov@omp.ru \
--cc=sergei.shtylyov@gmail.com \
/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).