public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel•org
To: Saeed Mahameed <saeed@kernel•org>
Cc: davem@davemloft•net, kuba@kernel•org, pabeni@redhat•com,
	edumazet@google•com, saeedm@nvidia•com, netdev@vger•kernel.org,
	tariqt@nvidia•com, dtatulea@nvidia•com
Subject: Re: [net 1/2] net/mlx5e: XDP, Fix fifo overrun on XDP_REDIRECT
Date: Thu, 17 Aug 2023 19:00:25 +0000	[thread overview]
Message-ID: <169229882525.13479.8981109425890919572.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230816204108.53819-2-saeed@kernel.org>

Hello:

This series was applied to netdev/net.git (main)
by Saeed Mahameed <saeedm@nvidia•com>:

On Wed, 16 Aug 2023 13:41:07 -0700 you wrote:
> From: Dragos Tatulea <dtatulea@nvidia•com>
> 
> Before this fix, running high rate traffic through XDP_REDIRECT
> with multibuf could overrun the fifo used to release the
> xdp frames after tx completion. This resulted in corrupted data
> being consumed on the free side.
> 
> [...]

Here is the summary with links:
  - [net,1/2] net/mlx5e: XDP, Fix fifo overrun on XDP_REDIRECT
    https://git.kernel.org/netdev/net/c/34a79876d9f7
  - [net,2/2] net/mlx5: Fix mlx5_cmd_update_root_ft() error flow
    https://git.kernel.org/netdev/net/c/0fd23db0cc74

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



  reply	other threads:[~2023-08-17 19:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-16 20:41 [pull request][net 0/2] mlx5 fixes 2023-08-16 Saeed Mahameed
2023-08-16 20:41 ` [net 1/2] net/mlx5e: XDP, Fix fifo overrun on XDP_REDIRECT Saeed Mahameed
2023-08-17 19:00   ` patchwork-bot+netdevbpf [this message]
2023-08-16 20:41 ` [net 2/2] net/mlx5: Fix mlx5_cmd_update_root_ft() error flow Saeed Mahameed

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=169229882525.13479.8981109425890919572.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=davem@davemloft$(echo .)net \
    --cc=dtatulea@nvidia$(echo .)com \
    --cc=edumazet@google$(echo .)com \
    --cc=kuba@kernel$(echo .)org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    --cc=saeed@kernel$(echo .)org \
    --cc=saeedm@nvidia$(echo .)com \
    --cc=tariqt@nvidia$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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