From: patchwork-bot+netdevbpf@kernel.org
To: Inochi Amaoto <inochiama@gmail.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, kgugala@antmicro.com,
mholenko@antmicro.com, gsomlo@gmail.com, joel@jms.id.au,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
looong.bin@gmail.com
Subject: Re: [PATCH net-next v3 0/2] net: ethernet: litex: minor improvment for the codebase
Date: Sat, 28 Feb 2026 03:40:25 +0000 [thread overview]
Message-ID: <177225002578.2855218.3920267376853849187.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260227003351.752934-1-inochiama@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 27 Feb 2026 08:33:46 +0800 you wrote:
> Improve the litex code for using the device managed function to register
> netdev and replace all the "pdev->dev" with dev pointer instead.
>
> Change from v2:
> - https://lore.kernel.org/netdev/20260119040446.741970-1-inochiama@gmail.com
> 1. Apply Andrew' tag
> 2. patch 2: wrap the line to match the characters limit
>
> [...]
Here is the summary with links:
- [net-next,v3,1/2] net: ethernet: litex: use devm_register_netdev() to register netdev
(no matching commit)
- [net-next,v3,2/2] net: ethernet: litex: use device pointer to simplify code.
https://git.kernel.org/netdev/net-next/c/621e3634dfab
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-02-28 3:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 0:33 [PATCH net-next v3 0/2] net: ethernet: litex: minor improvment for the codebase Inochi Amaoto
2026-02-27 0:33 ` [PATCH net-next v3 1/2] net: ethernet: litex: use devm_register_netdev() to register netdev Inochi Amaoto
2026-02-27 0:33 ` [PATCH net-next v3 2/2] net: ethernet: litex: use device pointer to simplify code Inochi Amaoto
2026-02-28 3:40 ` 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=177225002578.2855218.3920267376853849187.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gsomlo@gmail.com \
--cc=inochiama@gmail.com \
--cc=joel@jms.id.au \
--cc=kgugala@antmicro.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=looong.bin@gmail.com \
--cc=mholenko@antmicro.com \
--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