Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Benjamin Poirier <bpoirier@nvidia.com>
Cc: netdev@vger.kernel.org, shuah@kernel.org, corbet@lwn.net,
	j.vosburgh@gmail.com, andy@greyhouse.net, andrew@lunn.ch,
	f.fainelli@gmail.com, olteanv@gmail.com, jiri@resnulli.us,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, petrm@nvidia.com, danieller@nvidia.com,
	razor@blackwall.org, idosch@nvidia.com, jnixdorf-oss@avm.de,
	dcaratti@redhat.com, tobias@waldekranz.com,
	zdoychev@maxlinear.com, liuhangbin@gmail.com,
	linux-kselftest@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/6] selftests: Add TEST_INCLUDES directive and adjust tests to use it
Date: Wed, 31 Jan 2024 11:00:27 +0000	[thread overview]
Message-ID: <170669882741.1676.14282469125058737908.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240126232123.769784-1-bpoirier@nvidia.com>

Hello:

This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:

On Fri, 26 Jan 2024 18:21:17 -0500 you wrote:
> After commit 25ae948b4478 ("selftests/net: add lib.sh") but before commit
> 2114e83381d3 ("selftests: forwarding: Avoid failures to source
> net/lib.sh"), some net selftests encountered errors when they were being
> exported and run. This was because the new net/lib.sh was not exported
> along with the tests. The errors were crudely avoided by duplicating some
> content between net/lib.sh and net/forwarding/lib.sh in 2114e83381d3.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/6] selftests: Introduce Makefile variable to list shared bash scripts
    https://git.kernel.org/netdev/net-next/c/2a0683be5b4c
  - [net-next,v2,2/6] selftests: bonding: Add net/forwarding/lib.sh to TEST_INCLUDES
    https://git.kernel.org/netdev/net-next/c/6500780cffa7
  - [net-next,v2,3/6] selftests: team: Add shared library scripts to TEST_INCLUDES
    https://git.kernel.org/netdev/net-next/c/975b4a8b68ff
  - [net-next,v2,4/6] selftests: dsa: Replace test symlinks by wrapper script
    https://git.kernel.org/netdev/net-next/c/4a24560ad72f
  - [net-next,v2,5/6] selftests: forwarding: Redefine relative_path variable
    https://git.kernel.org/netdev/net-next/c/9f2af915916b
  - [net-next,v2,6/6] selftests: forwarding: Remove duplicated lib.sh content
    https://git.kernel.org/netdev/net-next/c/521ed1ce94bb

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-01-31 11:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-26 23:21 [PATCH net-next v2 0/6] selftests: Add TEST_INCLUDES directive and adjust tests to use it Benjamin Poirier
2024-01-26 23:21 ` [PATCH net-next v2 1/6] selftests: Introduce Makefile variable to list shared bash scripts Benjamin Poirier
2024-01-26 23:21 ` [PATCH net-next v2 2/6] selftests: bonding: Add net/forwarding/lib.sh to TEST_INCLUDES Benjamin Poirier
2024-01-27  0:28   ` Jay Vosburgh
2024-01-26 23:21 ` [PATCH net-next v2 3/6] selftests: team: Add shared library scripts " Benjamin Poirier
2024-01-26 23:21 ` [PATCH net-next v2 4/6] selftests: dsa: Replace test symlinks by wrapper script Benjamin Poirier
2024-01-26 23:21 ` [PATCH net-next v2 5/6] selftests: forwarding: Redefine relative_path variable Benjamin Poirier
2024-01-26 23:21 ` [PATCH net-next v2 6/6] selftests: forwarding: Remove duplicated lib.sh content Benjamin Poirier
2024-01-31 11: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=170669882741.1676.14282469125058737908.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=andy@greyhouse.net \
    --cc=bpoirier@nvidia.com \
    --cc=corbet@lwn.net \
    --cc=danieller@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=dcaratti@redhat.com \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=idosch@nvidia.com \
    --cc=j.vosburgh@gmail.com \
    --cc=jiri@resnulli.us \
    --cc=jnixdorf-oss@avm.de \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=liuhangbin@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=petrm@nvidia.com \
    --cc=razor@blackwall.org \
    --cc=shuah@kernel.org \
    --cc=tobias@waldekranz.com \
    --cc=zdoychev@maxlinear.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