From: patchwork-bot+netdevbpf@kernel.org
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, shuah@kernel.org, dsahern@kernel.org,
linux-kselftest@vger.kernel.org, roopa@nvidia.com,
nikolay@nvidia.com, idosch@nvidia.com, amitc@mellanox.com,
petrm@mellanox.com, lkp-owner@lists.01.org
Subject: Re: [PATCH net 0/2] selftests: net: add missing tests to Makefile
Date: Sat, 30 Apr 2022 01:00:12 +0000 [thread overview]
Message-ID: <165128041272.25380.10755696181043924363.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220428044511.227416-1-liuhangbin@gmail.com>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 28 Apr 2022 12:45:09 +0800 you wrote:
> When generating the selftests to another folder, the fixed tests are
> missing as they are not in Makefile. The missing tests are generated
> by command:
> $ for f in $(ls *.sh); do grep -q $f Makefile || echo $f; done
>
> I think there need a way to notify the developer when they created a new
> file in selftests folder. Maybe a bot like bluez.test.bot or kernel
> test robot could help do that?
>
> [...]
Here is the summary with links:
- [net,1/2] selftests/net: add missing tests to Makefile
https://git.kernel.org/netdev/net/c/38dcd9570d6f
- [net,2/2] selftests/net/forwarding: add missing tests to Makefile
https://git.kernel.org/netdev/net/c/f62c5acc800e
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-30 1:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 4:45 [PATCH net 0/2] selftests: net: add missing tests to Makefile Hangbin Liu
2022-04-28 4:45 ` [PATCH net 1/2] selftests/net: " Hangbin Liu
2022-04-28 4:45 ` [PATCH net 2/2] selftests/net/forwarding: " Hangbin Liu
2022-04-30 0:56 ` [PATCH net 0/2] selftests: net: " Jakub Kicinski
2022-05-17 6:23 ` Hangbin Liu
2022-05-17 19:45 ` Jakub Kicinski
2022-05-18 6:01 ` Hangbin Liu
2022-05-18 15:25 ` Jakub Kicinski
2022-05-19 3:13 ` Hangbin Liu
2022-04-30 1: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=165128041272.25380.10755696181043924363.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=amitc@mellanox.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=lkp-owner@lists.01.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=pabeni@redhat.com \
--cc=petrm@mellanox.com \
--cc=roopa@nvidia.com \
--cc=shuah@kernel.org \
/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