From: Krzysztof Kozlowski <krzk@kernel.org>
To: Arthur Crepin Leblond <arthur@marmottus.net>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v5 1/3] dt-bindings: net: wiznet,w5100: convert to DT schema
Date: Fri, 14 Aug 2026 09:15:27 +0200 [thread overview]
Message-ID: <20260814-violet-condor-of-expression-c491ed@quoll> (raw)
In-Reply-To: <20260813-wiznet-link-gpio-v5-1-ac8046f24413@marmottus.net>
On Thu, Aug 13, 2026 at 10:58:14AM +0200, Arthur Crepin Leblond wrote:
> Convert the Wiznet w5x00 SPI Ethernet controller binding from
> plain text to DT schema.
>
> Signed-off-by: Arthur Crepin Leblond <arthur@marmottus.net>
> ---
> .../devicetree/bindings/net/wiznet,w5100.yaml | 67 ++++++++++++++++++++++
> .../devicetree/bindings/net/wiznet,w5x00.txt | 50 ----------------
> 2 files changed, 67 insertions(+), 50 deletions(-)
Where did you explain reasons of dropping tags? Why would I need to do
the work twice?
<form letter>
This is a friendly reminder during the review process.
It looks like you received a tag and forgot to add it.
If you do not know the process, here is a short explanation:
Please add Acked-by/Reviewed-by/Tested-by tags when posting new
versions of patchset, under or above your Signed-off-by tag, unless
patch changed significantly (e.g. new properties added to the DT
bindings). Tag is "received", when provided in a message replied to you
on the mailing list. Tools like b4 can help here. However, there's no
need to repost patches *only* to add the tags. The upstream maintainer
will do that for tags received on the version they apply.
Please read:
https://elixir.bootlin.com/linux/v6.12-rc3/source/Documentation/process/submitting-patches.rst#L577
If a tag was not added on purpose, please state in the patch changelog
or cover letter why and what changed.
</form letter>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-08-14 7:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 8:58 [PATCH net-next v5 0/3] w5100: restore GPIO-based link detection Arthur Crepin Leblond
2026-08-13 8:58 ` [PATCH net-next v5 1/3] dt-bindings: net: wiznet,w5100: convert to DT schema Arthur Crepin Leblond
2026-08-14 7:15 ` Krzysztof Kozlowski [this message]
2026-08-14 10:32 ` Arthur Crepin Leblond
2026-08-14 8:58 ` sashiko-bot
2026-08-13 8:58 ` [PATCH net-next v5 2/3] dt-bindings: net: wiznet,w5100: add link status interrupt Arthur Crepin Leblond
2026-08-14 7:17 ` Krzysztof Kozlowski
2026-08-14 8:58 ` sashiko-bot
2026-08-13 8:58 ` [PATCH net-next v5 3/3] w5100: detect carrier state using link status bit and optional interrupt Arthur Crepin Leblond
2026-08-14 8:58 ` sashiko-bot
2026-08-14 11:02 ` Arthur Crepin Leblond
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=20260814-violet-condor-of-expression-c491ed@quoll \
--to=krzk@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=arnd@arndb.de \
--cc=arthur@marmottus.net \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@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