From: patchwork-bot+netdevbpf@kernel.org
To: Stefan Wahren <wahrenst@gmx.net>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH net-next V3 0/6] net: vertexcom: mse102x: Improve RX handling
Date: Tue, 13 May 2025 02:00:47 +0000 [thread overview]
Message-ID: <174710164798.1142511.4752177124866760612.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250509120435.43646-1-wahrenst@gmx.net>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 9 May 2025 14:04:29 +0200 you wrote:
> This series is the second part of two series for the Vertexcom driver.
> It contains some improvements for the RX handling of the Vertexcom MSE102x.
>
> Changes in V3:
> - Fix whitespace issue in patch 4
>
> Changes in V2:
> - Add Andrew's Reviewed-by to patch 1-2
> - Fix build issue reported by Jakub & kernel test bot in patch 2
> - Use Andrew's suggestion for netdev_warn_once in patch 2
> - Improve commit logs for patch 3 & 5
> - Add new patch 4 to compensate loss of invalid CMD counter
>
> [...]
Here is the summary with links:
- [net-next,V3,1/6] dt-bindings: vertexcom-mse102x: Fix IRQ type in example
https://git.kernel.org/netdev/net-next/c/a29a72866616
- [net-next,V3,2/6] net: vertexcom: mse102x: Add warning about IRQ trigger type
https://git.kernel.org/netdev/net-next/c/fed56943a8ba
- [net-next,V3,3/6] net: vertexcom: mse102x: Drop invalid cmd stats
https://git.kernel.org/netdev/net-next/c/aeb90c40ee9a
- [net-next,V3,4/6] net: vertexcom: mse102x: Implement flag for valid CMD
https://git.kernel.org/netdev/net-next/c/6ce9348468c5
- [net-next,V3,5/6] net: vertexcom: mse102x: Return code for mse102x_rx_pkt_spi
https://git.kernel.org/netdev/net-next/c/4ecf56f4b660
- [net-next,V3,6/6] net: vertexcom: mse102x: Simplify mse102x_rx_pkt_spi
https://git.kernel.org/netdev/net-next/c/8ea6e51e54c5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-05-13 2:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 12:04 [PATCH net-next V3 0/6] net: vertexcom: mse102x: Improve RX handling Stefan Wahren
2025-05-09 12:04 ` [PATCH net-next V3 1/6] dt-bindings: vertexcom-mse102x: Fix IRQ type in example Stefan Wahren
2025-05-09 16:01 ` Conor Dooley
2025-05-09 12:04 ` [PATCH net-next V3 2/6] net: vertexcom: mse102x: Add warning about IRQ trigger type Stefan Wahren
2025-05-09 12:04 ` [PATCH net-next V3 3/6] net: vertexcom: mse102x: Drop invalid cmd stats Stefan Wahren
2025-05-09 13:41 ` Andrew Lunn
2025-05-09 12:04 ` [PATCH net-next V3 4/6] net: vertexcom: mse102x: Implement flag for valid CMD Stefan Wahren
2025-05-09 13:42 ` Andrew Lunn
2025-05-09 12:04 ` [PATCH net-next V3 5/6] net: vertexcom: mse102x: Return code for mse102x_rx_pkt_spi Stefan Wahren
2025-05-09 12:04 ` [PATCH net-next V3 6/6] net: vertexcom: mse102x: Simplify mse102x_rx_pkt_spi Stefan Wahren
2025-05-13 2:00 ` patchwork-bot+netdevbpf [this message]
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=174710164798.1142511.4752177124866760612.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@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=kuba@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 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.