From: patchwork-bot+netdevbpf@kernel.org
To: Justin Chen <justin.chen@broadcom.com>
Cc: netdev@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com,
pabeni@redhat.com, kuba@kernel.org, edumazet@google.com,
davem@davemloft.net, andrew+netdev@lunn.ch,
florian.fainelli@broadcom.com
Subject: Re: [PATCH net-next v3 0/2] code clean up
Date: Tue, 27 Jan 2026 03:00:16 +0000 [thread overview]
Message-ID: <176948281659.660450.4225430749989258747.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260122194949.1145107-1-justin.chen@broadcom.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 22 Jan 2026 11:49:47 -0800 you wrote:
> Clean up and streamlined some code that is no longer needed due to
> older HW support being dropped.
>
> v2:
> Dropped a bug fix patch and sent to net instead so that it can be
> backported to stable.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/2] net: bcmasp: clean up some legacy logic
https://git.kernel.org/netdev/net-next/c/9271fc31901d
- [net-next,v3,2/2] net: bcmasp: streamline early exit in probe
https://git.kernel.org/netdev/net-next/c/1fd1281250c3
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:[~2026-01-27 3:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 19:49 [PATCH net-next v3 0/2] code clean up Justin Chen
2026-01-22 19:49 ` [PATCH net-next v3 1/2] net: bcmasp: clean up some legacy logic Justin Chen
2026-01-22 19:49 ` [PATCH net-next v3 2/2] net: bcmasp: streamline early exit in probe Justin Chen
2026-01-27 3: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=176948281659.660450.4225430749989258747.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=justin.chen@broadcom.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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