From: patchwork-bot+netdevbpf@kernel.org
To: Wei Fang <wei.fang@nxp.com>
Cc: shenwei.wang@nxp.com, xiaoning.wang@nxp.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, eric@nelint.com,
Frank.Li@nxp.com, imx@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 net-next 0/5] net: fec: do some cleanup for the driver
Date: Fri, 21 Nov 2025 02:50:20 +0000 [thread overview]
Message-ID: <176369342000.1872917.9969026361331291521.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251119025148.2817602-1-wei.fang@nxp.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 19 Nov 2025 10:51:43 +0800 you wrote:
> This patch set removes some unnecessary or invalid code from the FEC
> driver. See each patch for details.
>
> ---
> v3 changes:
> 1. Revert patch 2 to v1, fec_enet_register_offset_6ul still needs the
> "#ifdef" guard, otherwise, there are some build errors
> 2. Fix a typo in the commit message of patch 3
> 3. Collect Reviewed-by tag
> v2: https://lore.kernel.org/imx/20251117101921.1862427-1-wei.fang@nxp.com/
> v2 changes:
> 1. Improve the commit message
> 2. Remove the "#ifdef" guard for fec_enet_register_offset_6ul
> 3. Add a BUILD_BUG_ON() test to ensure that FEC_ENET_XDP_HEADROOM
> provides the required alignment.
> 4. Collect Reviewed-by tag
> v1: https://lore.kernel.org/imx/20251111100057.2660101-1-wei.fang@nxp.com/
>
> [...]
Here is the summary with links:
- [v3,net-next,1/5] net: fec: remove useless conditional preprocessor directives
https://git.kernel.org/netdev/net-next/c/3eea593b5597
- [v3,net-next,2/5] net: fec: simplify the conditional preprocessor directives
https://git.kernel.org/netdev/net-next/c/eef7b786bdab
- [v3,net-next,3/5] net: fec: remove struct fec_enet_priv_txrx_info
https://git.kernel.org/netdev/net-next/c/63083d597ada
- [v3,net-next,4/5] net: fec: remove rx_align from fec_enet_private
https://git.kernel.org/netdev/net-next/c/3bb06c8a461b
- [v3,net-next,5/5] net: fec: remove duplicate macros of the BD status
https://git.kernel.org/netdev/net-next/c/bd31490718b4
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-11-21 2:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 2:51 [PATCH v3 net-next 0/5] net: fec: do some cleanup for the driver Wei Fang
2025-11-19 2:51 ` [PATCH v3 net-next 1/5] net: fec: remove useless conditional preprocessor directives Wei Fang
2025-11-19 2:51 ` [PATCH v3 net-next 2/5] net: fec: simplify the " Wei Fang
2025-11-19 2:51 ` [PATCH v3 net-next 3/5] net: fec: remove struct fec_enet_priv_txrx_info Wei Fang
2025-11-19 2:51 ` [PATCH v3 net-next 4/5] net: fec: remove rx_align from fec_enet_private Wei Fang
2025-11-19 2:51 ` [PATCH v3 net-next 5/5] net: fec: remove duplicate macros of the BD status Wei Fang
2025-11-21 2:50 ` 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=176369342000.1872917.9969026361331291521.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric@nelint.com \
--cc=imx@lists.linux.dev \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shenwei.wang@nxp.com \
--cc=wei.fang@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 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.