From: Hardik Garg <hargar@linux.microsoft.com>
To: kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
decui@microsoft.com, krzk+dt@kernel.org, robh@kernel.org,
conor+dt@kernel.org, mhklinux@outlook.com
Cc: devicetree@vger.kernel.org, linux-hyperv@vger.kernel.org,
linux-kernel@vger.kernel.org, ssengar@linux.microsoft.com,
longli@microsoft.com, Naman Jain <namjain@linux.microsoft.com>,
hargar@microsoft.com, jacob.pan@linux.microsoft.com
Subject: Re: [PATCH v5 0/2] Add VMBus message connection ID support via DeviceTree
Date: Mon, 26 Jan 2026 16:12:48 -0800 [thread overview]
Message-ID: <ce54d00e-f252-48ac-8b0e-2992d1d4ef70@linux.microsoft.com> (raw)
In-Reply-To: <58cb22cb-b0c8-4694-b9e4-971aa7f0f972@linux.microsoft.com>
Just a gentle ping on this patch in case it got lost. I want to
check if anyone had a chance to look at it, or if there is
anything I should update or clarify.
I’ve also noticed a formatting issue in patch 2/2, which I
will address when sending a v6 along with any feedback.
Thanks,
Hardik
On 12/23/2025 3:05 PM, Hardik Garg wrote:
> This patch series adds support for reading the VMBus message
> connection ID from DeviceTree. The connection-id determines which
> hypervisor communication channel the guest should use to talk to
> the VMBus host.
>
> Changes in v5:
> - Updated subject line and commit description to clarify what
> connection ID is and why DeviceTree support is required
> - Addressed reviewer feedback about zero handling and binding
> constraints
> - Revised binding description to clarify version-based selection
> instead of using "defaults" language
> - Fixed checkpatch warnings (indentation and alignment)
prev parent reply other threads:[~2026-01-27 0:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 23:05 [PATCH v5 0/2] Add VMBus message connection ID support via DeviceTree Hardik Garg
2025-12-23 23:07 ` [PATCH v5 1/2] dt-bindings: microsoft: Add vmbus message-connection-id property Hardik Garg
2025-12-23 23:09 ` [PATCH v5 2/2] Drivers: hv: vmbus: retrieve connection-id from DeviceTree Hardik Garg
2026-01-27 0:12 ` Hardik Garg [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=ce54d00e-f252-48ac-8b0e-2992d1d4ef70@linux.microsoft.com \
--to=hargar@linux.microsoft.com \
--cc=conor+dt@kernel.org \
--cc=decui@microsoft.com \
--cc=devicetree@vger.kernel.org \
--cc=haiyangz@microsoft.com \
--cc=hargar@microsoft.com \
--cc=jacob.pan@linux.microsoft.com \
--cc=krzk+dt@kernel.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=mhklinux@outlook.com \
--cc=namjain@linux.microsoft.com \
--cc=robh@kernel.org \
--cc=ssengar@linux.microsoft.com \
--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