netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Petr Machata <petrm@nvidia.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, netdev@vger.kernel.org,
	linux-kselftest@vger.kernel.org, shuah@kernel.org,
	bpoirier@nvidia.com, liuhangbin@gmail.com,
	vladimir.oltean@nxp.com, idosch@nvidia.com,
	przemyslaw.kitszel@intel.com, willemb@google.com,
	mlxsw@nvidia.com
Subject: Re: [PATCH net-next v2 00/10] selftests: net: Introduce deferred commands
Date: Tue, 22 Oct 2024 11:50:32 +0000	[thread overview]
Message-ID: <172959783250.942320.16165385423521166401.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1729157566.git.petrm@nvidia.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Thu, 17 Oct 2024 11:45:42 +0200 you wrote:
> Recently, a defer helper was added to Python selftests. The idea is to keep
> cleanup commands close to their dirtying counterparts, thereby making it
> more transparent what is cleaning up what, making it harder to miss a
> cleanup, and make the whole cleanup business exception safe. All these
> benefits are applicable to bash as well, exception safety can be
> interpreted in terms of safety vs. a SIGINT.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,01/10] selftests: net: lib: Introduce deferred commands
    https://git.kernel.org/netdev/net-next/c/a6e263f125cd
  - [net-next,v2,02/10] selftests: forwarding: Add a fallback cleanup()
    https://git.kernel.org/netdev/net-next/c/b4b0549a4e59
  - [net-next,v2,03/10] selftests: forwarding: lib: Allow passing PID to stop_traffic()
    https://git.kernel.org/netdev/net-next/c/0e07d5dbfbd9
  - [net-next,v2,04/10] selftests: RED: Use defer for test cleanup
    (no matching commit)
  - [net-next,v2,05/10] selftests: TBF: Use defer for test cleanup
    https://git.kernel.org/netdev/net-next/c/a1b3741dcfd1
  - [net-next,v2,06/10] selftests: ETS: Use defer for test cleanup
    (no matching commit)
  - [net-next,v2,07/10] selftests: mlxsw: qos_mc_aware: Use defer for test cleanup
    (no matching commit)
  - [net-next,v2,08/10] selftests: mlxsw: qos_ets_strict: Use defer for test cleanup
    https://git.kernel.org/netdev/net-next/c/424745af5271
  - [net-next,v2,09/10] selftests: mlxsw: qos_max_descriptors: Use defer for test cleanup
    https://git.kernel.org/netdev/net-next/c/919419a8870b
  - [net-next,v2,10/10] selftests: mlxsw: devlink_trap_police: Use defer for test cleanup
    https://git.kernel.org/netdev/net-next/c/cebd281f3c75

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-22 11:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-17  9:45 [PATCH net-next v2 00/10] selftests: net: Introduce deferred commands Petr Machata
2024-10-17  9:45 ` [PATCH net-next v2 01/10] selftests: net: lib: " Petr Machata
2024-10-17  9:45 ` [PATCH net-next v2 02/10] selftests: forwarding: Add a fallback cleanup() Petr Machata
2024-10-17  9:45 ` [PATCH net-next v2 03/10] selftests: forwarding: lib: Allow passing PID to stop_traffic() Petr Machata
2024-10-17  9:45 ` [PATCH net-next v2 04/10] selftests: RED: Use defer for test cleanup Petr Machata
2024-10-17  9:45 ` [PATCH net-next v2 05/10] selftests: TBF: " Petr Machata
2024-10-17  9:45 ` [PATCH net-next v2 06/10] selftests: ETS: " Petr Machata
2024-10-17  9:45 ` [PATCH net-next v2 07/10] selftests: mlxsw: qos_mc_aware: " Petr Machata
2024-10-17  9:45 ` [PATCH net-next v2 08/10] selftests: mlxsw: qos_ets_strict: " Petr Machata
2024-10-17  9:45 ` [PATCH net-next v2 09/10] selftests: mlxsw: qos_max_descriptors: " Petr Machata
2024-10-17  9:45 ` [PATCH net-next v2 10/10] selftests: mlxsw: devlink_trap_police: " Petr Machata
2024-10-22 11: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=172959783250.942320.16165385423521166401.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bpoirier@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=liuhangbin@gmail.com \
    --cc=mlxsw@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=petrm@nvidia.com \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=shuah@kernel.org \
    --cc=vladimir.oltean@nxp.com \
    --cc=willemb@google.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).