All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Amit Cohen <amcohen@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, shuah@kernel.org,
	mlxsw@nvidia.com
Subject: Re: [PATCH net-next] selftests: fib_nexthops: Make the test more robust
Date: Fri, 13 May 2022 11:10:13 +0000	[thread overview]
Message-ID: <165244021308.2364.3445222668590598795.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220512131207.2617437-1-amcohen@nvidia.com>

Hello:

This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Thu, 12 May 2022 16:12:07 +0300 you wrote:
> Rarely some of the test cases fail. Make the test more robust by increasing
> the timeout of ping commands to 5 seconds.
> 
> Signed-off-by: Amit Cohen <amcohen@nvidia.com>
> ---
>  tools/testing/selftests/net/fib_nexthops.sh | 48 ++++++++++-----------
>  1 file changed, 24 insertions(+), 24 deletions(-)

Here is the summary with links:
  - [net-next] selftests: fib_nexthops: Make the test more robust
    https://git.kernel.org/netdev/net-next/c/49bb39bddad2

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-05-13 11:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-12 13:12 [PATCH net-next] selftests: fib_nexthops: Make the test more robust Amit Cohen
2022-05-12 13:31 ` Amit Cohen
2022-05-12 14:03   ` David Ahern
2022-05-12 14:28 ` Shuah Khan
2022-05-12 15:17   ` Amit Cohen
2022-05-12 16:40     ` Shuah Khan
2022-05-15 14:26       ` Amit Cohen
2022-05-17  3:15         ` Shuah Khan
2022-05-13 11: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=165244021308.2364.3445222668590598795.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=amcohen@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=mlxsw@nvidia.com \
    --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.