Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Joe Damato <jdamato@fastly.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, andrew+netdev@lunn.ch, shuah@kernel.org,
	linux-kselftest@vger.kernel.org, petrm@nvidia.com
Subject: Re: [PATCH net-next] selftests: netdevsim: add fib_notifications to Makefile
Date: Tue, 29 Oct 2024 12:35:48 -0700	[thread overview]
Message-ID: <ZyE5FHwhbU9V9-GG@LQ3V64L9R2> (raw)
In-Reply-To: <20241029192603.509295-1-kuba@kernel.org>

On Tue, Oct 29, 2024 at 12:26:03PM -0700, Jakub Kicinski wrote:
> Commit 19d36d2971e6 ("selftests: netdevsim: Add fib_notifications test")
> added the test but didn't include it in the Makefile.
> 
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> CC: andrew+netdev@lunn.ch
> CC: shuah@kernel.org
> CC: linux-kselftest@vger.kernel.org
> CC: petrm@nvidia.com
> ---
>  tools/testing/selftests/drivers/net/netdevsim/Makefile | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/tools/testing/selftests/drivers/net/netdevsim/Makefile b/tools/testing/selftests/drivers/net/netdevsim/Makefile
> index 5bace0b7fb57..cc08b220323f 100644
> --- a/tools/testing/selftests/drivers/net/netdevsim/Makefile
> +++ b/tools/testing/selftests/drivers/net/netdevsim/Makefile
> @@ -8,6 +8,7 @@ TEST_PROGS = devlink.sh \
>  	ethtool-pause.sh \
>  	ethtool-ring.sh \
>  	fib.sh \
> +	fib_notifications.sh \
>  	hw_stats_l3.sh \
>  	nexthop.sh \
>  	peer.sh \
> -- 
> 2.47.0

Reviewed-by: Joe Damato <jdamato@fastly.com>

  reply	other threads:[~2024-10-29 19:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-29 19:26 [PATCH net-next] selftests: netdevsim: add fib_notifications to Makefile Jakub Kicinski
2024-10-29 19:35 ` Joe Damato [this message]
2024-11-01  2:40 ` 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=ZyE5FHwhbU9V9-GG@LQ3V64L9R2 \
    --to=jdamato@fastly.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=petrm@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