bridge.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Nikolay Aleksandrov <razor@blackwall.org>
Cc: netdev@vger.kernel.org, kuba@kernel.org, roopa@nvidia.com,
	bridge@lists.linux.dev, edumazet@google.com, pabeni@redhat.com
Subject: Re: [PATCH net] selftests: net: bridge: increase IGMP/MLD exclude timeout membership interval
Date: Wed, 15 May 2024 10:50:29 +0000	[thread overview]
Message-ID: <171577022968.14646.2766126822531337987.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240513105257.769303-1-razor@blackwall.org>

Hello:

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

On Mon, 13 May 2024 13:52:57 +0300 you wrote:
> When running the bridge IGMP/MLD selftests on debug kernels we can get
> spurious errors when setting up the IGMP/MLD exclude timeout tests
> because the membership interval is just 3 seconds and the setup has 2
> seconds of sleep plus various validations, the one second that is left
> is not enough. Increase the membership interval from 3 to 5 seconds to
> make room for the setup validation and 2 seconds of sleep.
> 
> [...]

Here is the summary with links:
  - [net] selftests: net: bridge: increase IGMP/MLD exclude timeout membership interval
    https://git.kernel.org/netdev/net/c/06080ea23095

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



      parent reply	other threads:[~2024-05-15 10:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-13 10:52 [PATCH net] selftests: net: bridge: increase IGMP/MLD exclude timeout membership interval Nikolay Aleksandrov
2024-05-14  0:42 ` Hangbin Liu
2024-05-14  7:46   ` Nikolay Aleksandrov
2024-05-14 12:18     ` Hangbin Liu
2024-05-15 10:50 ` 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=171577022968.14646.2766126822531337987.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bridge@lists.linux.dev \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=razor@blackwall.org \
    --cc=roopa@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).