From: Petr Machata <petrm@nvidia.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Petr Machata <petrm@nvidia.com>, <netdev@vger.kernel.org>
Subject: Re: [TEST] vxlan brige test flakiness
Date: Mon, 8 Dec 2025 11:27:19 +0100 [thread overview]
Message-ID: <87qzt5w9kg.fsf@nvidia.com> (raw)
In-Reply-To: <20251205162610.40143536@kernel.org>
Jakub Kicinski <kuba@kernel.org> writes:
> On Fri, 5 Dec 2025 17:16:56 +0100 Petr Machata wrote:
>> OK, cool.
>>
>> I think the following patch would fix the issue. But I think it should
>> be thematically split into two parts, the lib.sh fix needs its own
>> explanation. Then there is a third patch to get rid of the
>> now-unnecessary vx_wait() helper.
>>
>> I think it makes sense to send it all as next material after you open it
>> in January. But if the issue is super annoying, I can send the two-part
>> fix now for net, and the cleanup in January for next.
>>
>> Let me know what you prefer.
>
> I think both the fix and the cleanup would be acceptable at this stage
> of the merge window. But no strong preference, I queued up the diff you
> shared as a local NIPA patch so we can see how it fares over the
> weekend. And it will get auto-ejected when you post the real thing.
Looks good so far, but not conclusive, there was a similarly long streak
before Dec 3. I'll check again tomorrow. If it's still green, I'll send
all three patches for net.
prev parent reply other threads:[~2025-12-08 10:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 17:50 [TEST] vxlan brige test flakiness Jakub Kicinski
2025-12-04 17:46 ` Petr Machata
2025-12-04 18:43 ` Jakub Kicinski
2025-12-05 16:16 ` Petr Machata
2025-12-06 0:26 ` Jakub Kicinski
2025-12-08 10:27 ` Petr Machata [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=87qzt5w9kg.fsf@nvidia.com \
--to=petrm@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).