From: Jakub Kicinski <kuba@kernel.org>
To: Stefan Wahren <wahrenst@gmx.net>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
netdev@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH net 2/5] dt-bindings: vertexcom-mse102x: Fix IRQ type in example
Date: Fri, 25 Apr 2025 17:30:48 -0700 [thread overview]
Message-ID: <20250425173048.36dfa282@kernel.org> (raw)
In-Reply-To: <20250423074553.8585-3-wahrenst@gmx.net>
On Wed, 23 Apr 2025 09:45:50 +0200 Stefan Wahren wrote:
> According to the MSE102x documentation the trigger type is a
> high level.
>
> Fixes: 2717566f6661 ("dt-bindings: net: add Vertexcom MSE102x support")
> Signed-off-by: Stefan Wahren <wahrenst@gmx.net>
I noticed after sending previous reply that the patchset already
got marked as changes requested. Let me use that as an excuse to
ask to drop this patch (and resend to net-next). Happy to oblige
if DT maintainers disagree but I'm not sure we should be treating
changes to an example as a fix.
next prev parent reply other threads:[~2025-04-26 0:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 7:45 [PATCH net 0/5] net: vertexcom: mse102x: Fix RX handling Stefan Wahren
2025-04-23 7:45 ` [PATCH net 1/5] net: vertexcom: mse102x: Fix possible stuck of SPI interrupt Stefan Wahren
2025-04-25 1:18 ` Jakub Kicinski
2025-04-25 7:35 ` Stefan Wahren
2025-04-26 0:17 ` Jakub Kicinski
2025-04-23 7:45 ` [PATCH net 2/5] dt-bindings: vertexcom-mse102x: Fix IRQ type in example Stefan Wahren
2025-04-26 0:30 ` Jakub Kicinski [this message]
2025-04-23 7:45 ` [PATCH net 3/5] net: vertexcom: mse102x: Fix LEN_MASK Stefan Wahren
2025-04-23 7:45 ` [PATCH net 4/5] net: vertexcom: mse102x: Add range check for CMD_RTS Stefan Wahren
2025-04-23 7:45 ` [PATCH net 5/5] net: vertexcom: mse102x: Fix RX error handling Stefan Wahren
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=20250425173048.36dfa282@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzk+dt@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=wahrenst@gmx.net \
/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).