netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: net: constrain number of 'reg' in ethernet ports
Date: Mon, 31 Oct 2022 17:03:44 -0700	[thread overview]
Message-ID: <20221031170344.07542bf5@kernel.org> (raw)
In-Reply-To: <20221028140326.43470-2-krzysztof.kozlowski@linaro.org>

On Fri, 28 Oct 2022 10:03:25 -0400 Krzysztof Kozlowski wrote:
> 'reg' without any constraints allows multiple items which is not the
> intention for Ethernet controller's port number.
> 
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>

There was some slightly confusing co-posting going on in the thread 
(this patch is a reply to patch 1/2?) so given Rob's questions / nits
I'll drop this from networking pw. Abundance of caution.

  parent reply	other threads:[~2022-11-01  0:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-28 14:03 [PATCH 1/2] dt-bindings: clock: qcom,gcc-ipq8074: use common GCC schema Krzysztof Kozlowski
2022-10-28 14:03 ` [PATCH] dt-bindings: net: constrain number of 'reg' in ethernet ports Krzysztof Kozlowski
2022-10-30 17:04   ` Oleksij Rempel
2022-10-31 18:57   ` Rob Herring
2022-11-02 15:48     ` Krzysztof Kozlowski
2022-11-01  0:03   ` Jakub Kicinski [this message]
2022-11-02 15:34     ` Krzysztof Kozlowski
2022-10-28 14:03 ` [PATCH 2/2] dt-bindings: clock: qcom: cleanup Krzysztof Kozlowski
2022-10-28 14:14   ` Jeffrey Hugo
2022-10-31 19:01   ` Rob Herring
2022-10-31 18:51 ` [PATCH 1/2] dt-bindings: clock: qcom,gcc-ipq8074: use common GCC schema Rob Herring
     [not found] ` <20221101194805.9EE0EC433C1@smtp.kernel.org>
2022-11-02 16:28   ` Krzysztof Kozlowski
  -- strict thread matches above, loose matches on Subject: below --
2022-10-28  1:54 [PATCH] dt-bindings: net: constrain number of 'reg' in ethernet ports Krzysztof Kozlowski

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=20221031170344.07542bf5@kernel.org \
    --to=kuba@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=netdev@vger.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).