From: Wei Fang <wei.fang@nxp.com>
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, xiaoning.wang@nxp.com, shenwei.wang@nxp.com,
netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-imx@nxp.com
Subject: [PATCH net-next 0/3] clean up the FEC driver
Date: Tue, 18 Jul 2023 17:09:25 +0800 [thread overview]
Message-ID: <20230718090928.2654347-1-wei.fang@nxp.com> (raw)
When reading the codes of the FEC driver recently, I found there are
some redundant or invalid codes, these codes make the FEC driver a
bit messy and not concise, so this patch set has cleaned up the FEC
driver. At present, I only found these, but I believe these are not
all, I will continue to clean up the FEC driver in the future.
Wei Fang (3):
net: fec: remove the remaining code of rx copybreak
net: fec: remove fec_set_mac_address() from fec_enet_init()
net: fec: remove unused members from struct fec_enet_private
drivers/net/ethernet/freescale/fec.h | 5 ---
drivers/net/ethernet/freescale/fec_main.c | 46 -----------------------
2 files changed, 51 deletions(-)
--
2.25.1
next reply other threads:[~2023-07-18 9:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 9:09 Wei Fang [this message]
2023-07-18 9:09 ` [PATCH net-next 1/3] net: fec: remove the remaining code of rx copybreak Wei Fang
2023-07-18 9:09 ` [PATCH net-next 2/3] net: fec: remove fec_set_mac_address() from fec_enet_init() Wei Fang
2023-07-18 9:09 ` [PATCH net-next 3/3] net: fec: remove unused members from struct fec_enet_private Wei Fang
2023-07-19 20:45 ` [PATCH net-next 0/3] clean up the FEC driver Simon Horman
2023-07-20 4:10 ` 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=20230718090928.2654347-1-wei.fang@nxp.com \
--to=wei.fang@nxp.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shenwei.wang@nxp.com \
--cc=xiaoning.wang@nxp.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;
as well as URLs for NNTP newsgroup(s).