public inbox for virtualization@lists.linux-foundation.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: netdev@vger.kernel.org, virtualization@lists.linux.dev,
	davem@davemloft.net, stefanha@redhat.com,
	linux-kernel@vger.kernel.org, leonardi@redhat.com
Subject: Re: [PATCH net v2] vsock/test: add a final full barrier after run all tests
Date: Mon, 12 Jan 2026 20:56:58 +0000	[thread overview]
Message-ID: <176825141802.1092878.8585699875911614513.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260108114419.52747-1-sgarzare@redhat.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu,  8 Jan 2026 12:44:19 +0100 you wrote:
> From: Stefano Garzarella <sgarzare@redhat.com>
> 
> If the last test fails, the other side still completes correctly,
> which could lead to false positives.
> 
> Let's add a final barrier that ensures that the last test has finished
> correctly on both sides, but also that the two sides agree on the
> number of tests to be performed.
> 
> [...]

Here is the summary with links:
  - [net,v2] vsock/test: add a final full barrier after run all tests
    https://git.kernel.org/netdev/net/c/c39a6a277e0e

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



      reply	other threads:[~2026-01-12 21:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-08 11:44 [PATCH net v2] vsock/test: add a final full barrier after run all tests Stefano Garzarella
2026-01-12 20:56 ` 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=176825141802.1092878.8585699875911614513.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=leonardi@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sgarzare@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=virtualization@lists.linux.dev \
    /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