All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jaehee Park <jhpark1013@gmail.com>
Cc: outreachy@lists.linux.dev, jdenham@redhat.com,
	roopa.prabhu@gmail.com, sbrivio@redhat.com,
	netdev@vger.kernel.org, roopa@nvidia.com, dsahern@gmail.com
Subject: Re: [PATCH net-next v4] selftests: net: vrf_strict_mode_test: add support to select a test to run
Date: Mon, 02 May 2022 09:00:12 +0000	[thread overview]
Message-ID: <165148201220.20737.6374754994100891007.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220429164658.GA656707@jaehee-ThinkPad-X1-Extreme>

Hello:

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

On Fri, 29 Apr 2022 12:46:58 -0400 you wrote:
> Add a boilerplate test loop to run all tests in
> vrf_strict_mode_test.sh. Add a -t flag that allows a selected test to
> run. Remove the vrf_strict_mode_tests function which is now unused.
> 
> Signed-off-by: Jaehee Park <jhpark1013@gmail.com>
> ---
> v2
> - Add a -t flag that allows a selected test to
> run.
> 
> [...]

Here is the summary with links:
  - [net-next,v4] selftests: net: vrf_strict_mode_test: add support to select a test to run
    https://git.kernel.org/netdev/net-next/c/a313f858ed36

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



      parent reply	other threads:[~2022-05-02  9:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-29 16:46 [PATCH net-next v4] selftests: net: vrf_strict_mode_test: add support to select a test to run Jaehee Park
2022-04-29 17:05 ` David Ahern
2022-05-02  9:00 ` 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=165148201220.20737.6374754994100891007.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=dsahern@gmail.com \
    --cc=jdenham@redhat.com \
    --cc=jhpark1013@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=outreachy@lists.linux.dev \
    --cc=roopa.prabhu@gmail.com \
    --cc=roopa@nvidia.com \
    --cc=sbrivio@redhat.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.