From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, davem@davemloft.net,
pabeni@redhat.com, f.fainelli@gmail.com, andrew@lunn.ch,
vivien.didelot@gmail.com, olteanv@gmail.com,
claudiu.manoil@nxp.com, alexandre.belloni@bootlin.com,
UNGLinuxDriver@microchip.com, tobias@waldekranz.com,
mattias.forsblad@gmail.com, roopa@nvidia.com, nikolay@nvidia.com,
jiri@nvidia.com, idosch@nvidia.com, troglobit@gmail.com,
kabel@kernel.org, ansuelsmth@gmail.com, dqfext@gmail.com,
kurt@linutronix.de
Subject: Re: [PATCH net-next 0/8] DSA selftests
Date: Sat, 23 Apr 2022 11:20:12 +0000 [thread overview]
Message-ID: <165071281235.17561.4364983512951885860.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220422101504.3729309-1-vladimir.oltean@nxp.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 22 Apr 2022 13:14:56 +0300 you wrote:
> When working on complex new features or reworks it becomes increasingly
> difficult to ensure there aren't regressions being introduced, and
> therefore it would be nice if we could go over the functionality we
> already have and write some tests for it.
>
> Verbally I know from Tobias Waldekranz that he has been working on some
> selftests for DSA, yet I have never seen them, so here I am adding some
> tests I have written which have been useful for me. The list is by no
> means complete (it only covers elementary functionality), but it's still
> good to have as a starting point. I also borrowed some refactoring
> changes from Joachim Wiberg that he submitted for his "net: bridge:
> forwarding of unknown IPv4/IPv6/MAC BUM traffic" series, but not the
> entirety of his selftests. I now think that his selftests have some
> overlap with bridge_vlan_unaware.sh and bridge_vlan_aware.sh and they
> should be more tightly integrated with each other - yet I didn't do that
> either :). Another issue I had with his selftests was that they jumped
> straight ahead to configure brport flags on br0 (a radical new idea
> still at RFC status) while we have bigger problems, and we don't have
> nearly enough coverage for the *existing* functionality.
>
> [...]
Here is the summary with links:
- [net-next,1/8] selftests: forwarding: add option to run tests with stable MAC addresses
https://git.kernel.org/netdev/net-next/c/b343734ee265
- [net-next,2/8] selftests: forwarding: add TCPDUMP_EXTRA_FLAGS to lib.sh
https://git.kernel.org/netdev/net-next/c/fe32dffdcd33
- [net-next,3/8] selftests: forwarding: multiple instances in tcpdump helper
https://git.kernel.org/netdev/net-next/c/6182c5c5098f
- [net-next,4/8] selftests: forwarding: add helpers for IP multicast group joins/leaves
https://git.kernel.org/netdev/net-next/c/f23cddc72294
- [net-next,5/8] selftests: forwarding: add helper for retrieving IPv6 link-local address of interface
https://git.kernel.org/netdev/net-next/c/a5114df6c613
- [net-next,6/8] selftests: forwarding: add a no_forwarding.sh test
https://git.kernel.org/netdev/net-next/c/476a4f05d9b8
- [net-next,7/8] selftests: forwarding: add a test for local_termination.sh
https://git.kernel.org/netdev/net-next/c/90b9566aa5cd
- [net-next,8/8] selftests: drivers: dsa: add a subset of forwarding selftests
https://git.kernel.org/netdev/net-next/c/07c8a2dd69f6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-04-23 11:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 10:14 [PATCH net-next 0/8] DSA selftests Vladimir Oltean
2022-04-22 10:14 ` [PATCH net-next 1/8] selftests: forwarding: add option to run tests with stable MAC addresses Vladimir Oltean
2022-04-22 10:14 ` [PATCH net-next 2/8] selftests: forwarding: add TCPDUMP_EXTRA_FLAGS to lib.sh Vladimir Oltean
2022-04-22 10:14 ` [PATCH net-next 3/8] selftests: forwarding: multiple instances in tcpdump helper Vladimir Oltean
2022-04-22 10:15 ` [PATCH net-next 4/8] selftests: forwarding: add helpers for IP multicast group joins/leaves Vladimir Oltean
2022-04-22 10:15 ` [PATCH net-next 5/8] selftests: forwarding: add helper for retrieving IPv6 link-local address of interface Vladimir Oltean
2022-04-22 10:15 ` [PATCH net-next 6/8] selftests: forwarding: add a no_forwarding.sh test Vladimir Oltean
2022-04-22 10:15 ` [PATCH net-next 7/8] selftests: forwarding: add a test for local_termination.sh Vladimir Oltean
2022-04-22 10:15 ` [PATCH net-next 8/8] selftests: drivers: dsa: add a subset of forwarding selftests Vladimir Oltean
2022-04-22 10:22 ` [PATCH net-next 0/8] DSA selftests Vladimir Oltean
2022-04-23 11: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=165071281235.17561.4364983512951885860.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=dqfext@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=idosch@nvidia.com \
--cc=jiri@nvidia.com \
--cc=kabel@kernel.org \
--cc=kuba@kernel.org \
--cc=kurt@linutronix.de \
--cc=mattias.forsblad@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=roopa@nvidia.com \
--cc=tobias@waldekranz.com \
--cc=troglobit@gmail.com \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@nxp.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