All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hangbin Liu <liuhangbin@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
	Paolo Abeni <pabeni@redhat.com>, Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH net 0/2] selftests: net: add missing tests to Makefile
Date: Wed, 4 May 2022 11:00:29 +0800	[thread overview]
Message-ID: <YnHsTdgxTKHiDQSJ@Laptop-X1> (raw)
In-Reply-To: <20220429175604.249bb2fb@kernel.org>

On Fri, Apr 29, 2022 at 05:56:04PM -0700, Jakub Kicinski wrote:
> On Thu, 28 Apr 2022 12:45:09 +0800 Hangbin Liu 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?
> 
> Our netdev patch checks are here:
> 
> https://github.com/kuba-moo/nipa/tree/master/tests/patch
> 
> in case you're willing to code it up and post a PR.

Thanks, I will check this and post MR when have time.

Hangbin

  reply	other threads:[~2022-05-04  3:00 UTC|newest]

Thread overview: 11+ 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-04  3:00   ` Hangbin Liu [this message]
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

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=YnHsTdgxTKHiDQSJ@Laptop-X1 \
    --to=liuhangbin@gmail.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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 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.