From: Naman Jain <namjain@linux.microsoft.com>
To: Dexuan Cui <decui@microsoft.com>,
KY Srinivasan <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Wei Liu <wei.liu@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: "linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@kernel.org" <stable@kernel.org>,
Saurabh Sengar <ssengar@linux.microsoft.com>,
Michael Kelley <mhklinux@outlook.com>
Subject: Re: [PATCH v5 2/2] Drivers: hv: Make the sysfs node size for the ring buffer dynamic
Date: Tue, 22 Apr 2025 19:56:12 +0530 [thread overview]
Message-ID: <599c3a2a-c42b-484d-aa9d-0a9313c10ce8@linux.microsoft.com> (raw)
In-Reply-To: <BL4PR21MB4627622A03EB8E5D68EC20E4BFBF2@BL4PR21MB4627.namprd21.prod.outlook.com>
On 4/18/2025 6:43 AM, Dexuan Cui wrote:
>> From: Naman Jain <namjain@linux.microsoft.com>
>> Sent: Tuesday, April 15, 2025 9:45 AM
>> [...]
>> actual ring buffer size for each channel. This will ensure that
>> fstat() on ring sysfs node always return the correct size of
> s/return/returns/
>> [...]
>
> Reviewed-by: Dexuan Cui <decui@microsoft.com>
Thanks. I'll make the required changes.
Regards,
Naman
prev parent reply other threads:[~2025-04-22 14:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 16:44 [PATCH v5 0/2] uio_hv_generic: Fix ring buffer sysfs creation path Naman Jain
2025-04-15 16:44 ` [PATCH v5 1/2] uio_hv_generic: Fix sysfs creation path for ring buffer Naman Jain
2025-04-18 1:09 ` Dexuan Cui
2025-04-22 14:25 ` Naman Jain
2025-04-15 16:44 ` [PATCH v5 2/2] Drivers: hv: Make the sysfs node size for the ring buffer dynamic Naman Jain
2025-04-18 1:13 ` Dexuan Cui
2025-04-22 14:26 ` Naman Jain [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=599c3a2a-c42b-484d-aa9d-0a9313c10ce8@linux.microsoft.com \
--to=namjain@linux.microsoft.com \
--cc=decui@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhklinux@outlook.com \
--cc=ssengar@linux.microsoft.com \
--cc=stable@kernel.org \
--cc=stephen@networkplumber.org \
--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