public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Liao Yuanhong <liaoyuanhong@vivo.com>
To: Joe Damato <joe@dama.to>
Cc: Stefano Garzarella <sgarzare@redhat.com>,
	Paolo Abeni <pabeni@redhat.com>,
	Konstantin Shkolnyy <kshk@linux.ibm.com>,
	"open list:VM SOCKETS (AF_VSOCK)"
	<virtualization@lists.linux.dev>,
	"open list:VM SOCKETS (AF_VSOCK)" <netdev@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] vsock/test: Remove redundant semicolons
Date: Wed, 13 Aug 2025 14:56:58 +0800	[thread overview]
Message-ID: <a161ad99-8941-4213-95e3-86c5ef948215@vivo.com> (raw)
In-Reply-To: <aJt91SSkBO486bg5@MacBook-Air.local>

On 8/13/2025 1:45 AM, Joe Damato wrote:

> [You don't often get email from joe@dama.to. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> On Tue, Aug 12, 2025 at 12:01:15PM +0800, Liao Yuanhong wrote:
>> Remove unnecessary semicolons.
>>
>> Fixes: 86814d8ffd55f ("vsock/test: verify socket options after setting them")
>> Signed-off-by: Liao Yuanhong <liaoyuanhong@vivo.com>
>> ---
>>   tools/testing/vsock/util.c | 1 -
>>   1 file changed, 1 deletion(-)
>>
>> diff --git a/tools/testing/vsock/util.c b/tools/testing/vsock/util.c
>> index 7b861a8e997a..d843643ced6b 100644
>> --- a/tools/testing/vsock/util.c
>> +++ b/tools/testing/vsock/util.c
>> @@ -756,7 +756,6 @@ void setsockopt_ull_check(int fd, int level, int optname,
>>   fail:
>>        fprintf(stderr, "%s  val %llu\n", errmsg, val);
>>        exit(EXIT_FAILURE);
>> -;
>>   }
> This isn't a fixes since it doesn't fix a bug; it's cleanup so I'd probably
> target net-next and drop the fixes tag.

Do you need me to resend the v2 version without the fixes tag?


Thanks,

Liao


  reply	other threads:[~2025-08-13  6:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-12  4:01 [PATCH] vsock/test: Remove redundant semicolons Liao Yuanhong
2025-08-12 17:45 ` Joe Damato
2025-08-13  6:56   ` Liao Yuanhong [this message]
2025-08-27  7:45     ` Stefano Garzarella

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=a161ad99-8941-4213-95e3-86c5ef948215@vivo.com \
    --to=liaoyuanhong@vivo.com \
    --cc=joe@dama.to \
    --cc=kshk@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sgarzare@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