From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: j.vosburgh@gmail.com, vfalico@gmail.com, andy@greyhouse.net,
shuah@kernel.org, kuba@kernel.org, liuhangbin@gmail.com,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] selftests/bonding: re-add lladdr target test
Date: Fri, 23 Sep 2022 14:10:16 +0000 [thread overview]
Message-ID: <166394221699.18573.18054139188469148797.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220923082306.2468081-1-matthieu.baerts@tessares.net>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 23 Sep 2022 10:23:06 +0200 you wrote:
> It looks like this test has been accidentally dropped when resolving
> conflicts in this Makefile.
>
> Most probably because there were 3 different patches modifying this file
> in parallel:
>
> commit 152e8ec77640 ("selftests/bonding: add a test for bonding lladdr target")
> commit bbb774d921e2 ("net: Add tests for bonding and team address list management")
> commit 2ffd57327ff1 ("selftests: bonding: cause oops in bond_rr_gen_slave_id")
>
> [...]
Here is the summary with links:
- [net-next] selftests/bonding: re-add lladdr target test
https://git.kernel.org/netdev/net-next/c/aacdecda9eb4
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-09-23 14:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 8:23 [PATCH net-next] selftests/bonding: re-add lladdr target test Matthieu Baerts
2022-09-23 9:21 ` Hangbin Liu
2022-09-23 13:25 ` Jakub Kicinski
2022-09-23 14:10 ` 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=166394221699.18573.18054139188469148797.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andy@greyhouse.net \
--cc=j.vosburgh@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=matthieu.baerts@tessares.net \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=vfalico@gmail.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.