[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ce54d00e-f252-48ac-8b0e-2992d1d4ef70@linux.microsoft.com>
Date: Mon, 26 Jan 2026 16:12:48 -0800
From: Hardik Garg <hargar@...ux.microsoft.com>
To: kys@...rosoft.com, haiyangz@...rosoft.com, wei.liu@...nel.org,
decui@...rosoft.com, krzk+dt@...nel.org, robh@...nel.org,
conor+dt@...nel.org, mhklinux@...look.com
Cc: devicetree@...r.kernel.org, linux-hyperv@...r.kernel.org,
linux-kernel@...r.kernel.org, ssengar@...ux.microsoft.com,
longli@...rosoft.com, Naman Jain <namjain@...ux.microsoft.com>,
hargar@...rosoft.com, jacob.pan@...ux.microsoft.com
Subject: Re: [PATCH v5 0/2] Add VMBus message connection ID support via
DeviceTree
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)
Powered by blists - more mailing lists