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) 

Reply via email to