From: patchwork-bot+netdevbpf@kernel.org
To: Lukasz Majewski <lukma@denx.de>
Cc: kuba@kernel.org, netdev@vger.kernel.org, pabeni@redhat.com,
edumazet@google.com, olteanv@gmail.com, davem@davemloft.net,
o.rempel@pengutronix.de, Tristram.Ha@microchip.com,
bigeasy@linutronix.de, r-gunasekaran@ti.com, horms@kernel.org,
n.zhandarovich@fintech.ru, m-karicheri2@ti.com,
Arvid.Brodin@xdin.com, dan.carpenter@linaro.org,
ricardo@marliere.net, casper.casan@gmail.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
liuhangbin@gmail.com, tanggeliang@kylinos.cn, shuah@kernel.org
Subject: Re: [PATCH net-next] selftests: hsr: Extend the hsr_ping.sh test to use fixed MAC addresses
Date: Thu, 06 Jun 2024 02:30:32 +0000 [thread overview]
Message-ID: <171764103211.23267.2425387874478992852.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240603093322.3150030-1-lukma@denx.de>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 3 Jun 2024 11:33:21 +0200 you wrote:
> Fixed MAC addresses help with debugging as last four bytes identify the
> network namespace.
>
> Signed-off-by: Lukasz Majewski <lukma@denx.de>
> ---
> tools/testing/selftests/net/hsr/hsr_ping.sh | 9 +++++++++
> 1 file changed, 9 insertions(+)
Here is the summary with links:
- [net-next] selftests: hsr: Extend the hsr_ping.sh test to use fixed MAC addresses
https://git.kernel.org/netdev/net-next/c/ed20142ed68c
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:[~2024-06-06 2:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 9:33 [PATCH net-next] selftests: hsr: Extend the hsr_ping.sh test to use fixed MAC addresses Lukasz Majewski
2024-06-03 9:33 ` [PATCH net-next] selftests: hsr: Extend the hsr_redbox.sh " Lukasz Majewski
2024-06-06 2:27 ` Jakub Kicinski
2024-06-06 2:30 ` patchwork-bot+netdevbpf
2024-06-06 2:30 ` 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=171764103211.23267.2425387874478992852.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Arvid.Brodin@xdin.com \
--cc=Tristram.Ha@microchip.com \
--cc=bigeasy@linutronix.de \
--cc=casper.casan@gmail.com \
--cc=dan.carpenter@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=lukma@denx.de \
--cc=m-karicheri2@ti.com \
--cc=n.zhandarovich@fintech.ru \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=r-gunasekaran@ti.com \
--cc=ricardo@marliere.net \
--cc=shuah@kernel.org \
--cc=tanggeliang@kylinos.cn \
/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.