linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Xuewei Niu <niuxuewei.nxw@antgroup.com>
Cc: kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
	decui@microsoft.com, sgarzare@redhat.com, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, linux-hyperv@vger.kernel.org,
	virtualization@lists.linux.dev, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, niuxuewei97@gmail.com
Subject: Re: [PATCH net-next v6 0/4] vsock: Introduce SIOCINQ ioctl support
Date: Thu, 10 Jul 2025 02:50:21 +0000	[thread overview]
Message-ID: <175211582149.967127.15893085355857485590.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250708-siocinq-v6-0-3775f9a9e359@antgroup.com>

Hello:

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

On Tue, 08 Jul 2025 14:36:10 +0800 you wrote:
> Introduce SIOCINQ ioctl support for vsock, indicating the length of unread
> bytes.
> 
> Similar with SIOCOUTQ ioctl, the information is transport-dependent.
> 
> The first patch adds SIOCINQ ioctl support in AF_VSOCK.
> 
> [...]

Here is the summary with links:
  - [net-next,v6,1/4] hv_sock: Return the readable bytes in hvs_stream_has_data()
    https://git.kernel.org/netdev/net-next/c/f0c5827d07cb
  - [net-next,v6,2/4] vsock: Add support for SIOCINQ ioctl
    https://git.kernel.org/netdev/net-next/c/f7c722659275
  - [net-next,v6,3/4] test/vsock: Add retry mechanism to ioctl wrapper
    https://git.kernel.org/netdev/net-next/c/53548d6bffac
  - [net-next,v6,4/4] test/vsock: Add ioctl SIOCINQ tests
    https://git.kernel.org/netdev/net-next/c/613165683d34

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



      parent reply	other threads:[~2025-07-10  2:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-08  6:36 [PATCH net-next v6 0/4] vsock: Introduce SIOCINQ ioctl support Xuewei Niu
2025-07-08  6:36 ` [PATCH net-next v6 1/4] hv_sock: Return the readable bytes in hvs_stream_has_data() Xuewei Niu
2025-07-08 10:49   ` Stefano Garzarella
2025-07-09 23:23   ` Wei Liu
2025-07-08  6:36 ` [PATCH net-next v6 2/4] vsock: Add support for SIOCINQ ioctl Xuewei Niu
2025-07-08 10:52   ` Stefano Garzarella
2025-07-09 15:00   ` Luigi Leonardi
2025-07-08  6:36 ` [PATCH net-next v6 3/4] test/vsock: Add retry mechanism to ioctl wrapper Xuewei Niu
2025-07-08 10:54   ` Stefano Garzarella
2025-07-09 15:02   ` Luigi Leonardi
2025-07-08  6:36 ` [PATCH net-next v6 4/4] test/vsock: Add ioctl SIOCINQ tests Xuewei Niu
2025-07-08 10:57   ` Stefano Garzarella
2025-07-09 15:05   ` Luigi Leonardi
2025-07-10  2: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=175211582149.967127.15893085355857485590.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=decui@microsoft.com \
    --cc=edumazet@google.com \
    --cc=haiyangz@microsoft.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kys@microsoft.com \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=niuxuewei.nxw@antgroup.com \
    --cc=niuxuewei97@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=sgarzare@redhat.com \
    --cc=virtualization@lists.linux.dev \
    --cc=wei.liu@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).