Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Wei Fang <wei.fang@nxp.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, claudiu.manoil@nxp.com,
	vladimir.oltean@nxp.com, ast@kernel.org, daniel@iogearbox.net,
	hawk@kernel.org, john.fastabend@gmail.com,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	bpf@vger.kernel.org, stable@vger.kernel.org, imx@lists.linux.dev,
	rkannoth@marvell.com, maciej.fijalkowski@intel.com,
	sbhatta@marvell.com
Subject: Re: [PATCH v4 net 0/4] net: enetc: fix some issues of XDP
Date: Fri, 11 Oct 2024 23:10:37 +0000	[thread overview]
Message-ID: <172868823798.3022673.12555196619496789739.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241010092056.298128-1-wei.fang@nxp.com>

Hello:

This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 10 Oct 2024 17:20:52 +0800 you wrote:
> We found some bugs when testing the XDP function of enetc driver,
> and these bugs are easy to reproduce. This is not only causes XDP
> to not work, but also the network cannot be restored after exiting
> the XDP program. So the patch set is mainly to fix these bugs. For
> details, please see the commit message of each patch.
> 
> 
> [...]

Here is the summary with links:
  - [v4,net,1/4] net: enetc: remove xdp_drops statistic from enetc_xdp_drop()
    https://git.kernel.org/netdev/net/c/412950d5746f
  - [v4,net,2/4] net: enetc: block concurrent XDP transmissions during ring reconfiguration
    https://git.kernel.org/netdev/net/c/c728a95ccf2a
  - [v4,net,3/4] net: enetc: disable Tx BD rings after they are empty
    https://git.kernel.org/netdev/net/c/0a93f2ca4be6
  - [v4,net,4/4] net: enetc: disable NAPI after all rings are disabled
    https://git.kernel.org/netdev/net/c/6b58fadd44aa

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-10-11 23:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-10  9:20 [PATCH v4 net 0/4] net: enetc: fix some issues of XDP Wei Fang
2024-10-10  9:20 ` [PATCH v4 net 1/4] net: enetc: remove xdp_drops statistic from enetc_xdp_drop() Wei Fang
2024-10-10  9:20 ` [PATCH v4 net 2/4] net: enetc: block concurrent XDP transmissions during ring reconfiguration Wei Fang
2024-10-11 14:38   ` Vladimir Oltean
2024-10-10  9:20 ` [PATCH v4 net 3/4] net: enetc: disable Tx BD rings after they are empty Wei Fang
2024-10-11 14:40   ` Vladimir Oltean
2024-10-10  9:20 ` [PATCH v4 net 4/4] net: enetc: disable NAPI after all rings are disabled Wei Fang
2024-10-11 14:42   ` Vladimir Oltean
2024-10-11 23:10 ` 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=172868823798.3022673.12555196619496789739.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=claudiu.manoil@nxp.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hawk@kernel.org \
    --cc=imx@lists.linux.dev \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maciej.fijalkowski@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rkannoth@marvell.com \
    --cc=sbhatta@marvell.com \
    --cc=stable@vger.kernel.org \
    --cc=vladimir.oltean@nxp.com \
    --cc=wei.fang@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