On Wed, May 28, 2025 at 02:33:25PM -0700, Hardik Garg wrote:

The connection-id determines which hypervisor communication channel the
guest should use to talk to the VMBus host. This patch adds support to
read this value from the device tree where it exists as a property under
the vmbus node with the compatible ID "microsoft,message-connection-id".

Add Documentation for "microsoft,message-connection-id"

Reading from device tree allows platforms to specify their preferred
communication channel, making it more flexible. If the property is
not found in the device tree, use the default connection ID
(VMBUS_MESSAGE_CONNECTION_ID or VMBUS_MESSAGE_CONNECTION_ID_4
based on protocol version).

Cc: <stable@kernel.org> # 6.14, 6.12

I don't see it as as bug which needs to be backported on certain branches only.
You can rebase your changes on linux-next or hyperv-next and resend.

Also,

s/device tree/DeviceTree/g


- Saurabh