From: Stefan Wahren <wahrenst@gmx.net>
To: 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>
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
Stefan Wahren <wahrenst@gmx.net>
Subject: [PATCH net V2 0/4] net: vertexcom: mse102x: Fix RX handling
Date: Wed, 30 Apr 2025 15:30:39 +0200 [thread overview]
Message-ID: <20250430133043.7722-1-wahrenst@gmx.net> (raw)
This series is the first part of two series for the Vertexcom driver.
It contains substantial fixes for the RX handling of the Vertexcom MSE102x.
Changes in V2:
- clarify cover letter
- add footnote to Patch 1
- postpone DT binding changes to second series as suggested by Jakub K.
Stefan Wahren (4):
net: vertexcom: mse102x: Fix possible stuck of SPI interrupt
net: vertexcom: mse102x: Fix LEN_MASK
net: vertexcom: mse102x: Add range check for CMD_RTS
net: vertexcom: mse102x: Fix RX error handling
drivers/net/ethernet/vertexcom/mse102x.c | 36 +++++++++++++++++++-----
1 file changed, 29 insertions(+), 7 deletions(-)
--
2.34.1
next reply other threads:[~2025-04-30 13:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 13:30 Stefan Wahren [this message]
2025-04-30 13:30 ` [PATCH net V2 1/4] net: vertexcom: mse102x: Fix possible stuck of SPI interrupt Stefan Wahren
2025-04-30 13:48 ` Andrew Lunn
2025-04-30 13:30 ` [PATCH net V2 2/4] net: vertexcom: mse102x: Fix LEN_MASK Stefan Wahren
2025-04-30 13:47 ` Andrew Lunn
2025-04-30 13:30 ` [PATCH net V2 3/4] net: vertexcom: mse102x: Add range check for CMD_RTS Stefan Wahren
2025-04-30 13:47 ` Andrew Lunn
2025-04-30 13:30 ` [PATCH net V2 4/4] net: vertexcom: mse102x: Fix RX error handling Stefan Wahren
2025-04-30 13:47 ` Andrew Lunn
2025-04-30 14:27 ` Stefan Wahren
2025-05-01 14:40 ` [PATCH net V2 0/4] net: vertexcom: mse102x: Fix RX handling 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=20250430133043.7722-1-wahrenst@gmx.net \
--to=wahrenst@gmx.net \
--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=kuba@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.