All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Dimitri Daskalakis <dimitri.daskalakis1@gmail.com>
Cc: davem@davemloft.net, andrew+netdev@lunn.ch, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, shuah@kernel.org,
	netdev@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next] selftests: drv-net: remove duplicate functions in hds.py
Date: Tue, 15 Sep 2026 23:20:06 +0000	[thread overview]
Message-ID: <178951440613.2314577.9685453307145210984.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260911224255.3675903-1-dimitri.daskalakis1@gmail.com>

Hello:

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

On Fri, 11 Sep 2026 15:42:55 -0700 you wrote:
> From: Dimitri Daskalakis <daskald@meta.com>
> 
> There were duplicate definitions of the enabled_set_xdp and set_xdp
> test methods. The two enabled_set_xdp copies were identical apart from
> a comment and whitespace.
> 
> The set_xdp copies differed by a reset of the hds configuration.
> commit ee3ae27721fb ("selftests: drv-net: hds: restore hds settings")
> introduced the config reset, but this was shadowed by the copy.
> 
> [...]

Here is the summary with links:
  - [net-next] selftests: drv-net: remove duplicate functions in hds.py
    https://git.kernel.org/netdev/net-next/c/3661253d2253

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



      reply	other threads:[~2026-09-15 23:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11 22:42 [PATCH net-next] selftests: drv-net: remove duplicate functions in hds.py Dimitri Daskalakis
2026-09-15 23:20 ` 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=178951440613.2314577.9685453307145210984.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=dimitri.daskalakis1@gmail.com \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@kernel.org \
    /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.