From: Inochi Amaoto <inochiama@gmail.com>
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>,
Karol Gugala <kgugala@antmicro.com>,
Mateusz Holenko <mholenko@antmicro.com>,
Gabriel Somlo <gsomlo@gmail.com>, Joel Stanley <joel@jms.id.au>
Cc: Inochi Amaoto <inochiama@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Longbin Li <looong.bin@gmail.com>
Subject: [PATCH net-next v3 0/2] net: ethernet: litex: minor improvment for the codebase
Date: Fri, 27 Feb 2026 08:33:46 +0800 [thread overview]
Message-ID: <20260227003351.752934-1-inochiama@gmail.com> (raw)
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
Change from v1:
- https://lore.kernel.org/netdev/20260116003150.183070-1-inochiama@gmail.com/
1. separate the original patch into two patches.
Inochi Amaoto (2):
net: ethernet: litex: use devm_register_netdev() to register netdev
net: ethernet: litex: use device pointer to simplify code.
drivers/net/ethernet/litex/litex_liteeth.c | 21 +++++++--------------
1 file changed, 7 insertions(+), 14 deletions(-)
--
2.53.0
next reply other threads:[~2026-02-27 0:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 0:33 Inochi Amaoto [this message]
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 ` [PATCH net-next v3 0/2] net: ethernet: litex: minor improvment for the codebase 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=20260227003351.752934-1-inochiama@gmail.com \
--to=inochiama@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gsomlo@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