[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250529054352.GA29740@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
Date: Wed, 28 May 2025 22:43:52 -0700
From: Saurabh Singh Sengar <ssengar@...ux.microsoft.com>
To: Hardik Garg <hargar@...ux.microsoft.com>
Cc: kys@...rosoft.com, haiyangz@...rosoft.com, wei.liu@...nel.org,
decui@...rosoft.com, romank@...ux.microsoft.com,
linux-hyperv@...r.kernel.org, linux-kernel@...r.kernel.org,
stable@...nel.org, ssengar@...rosoft.com, apais@...rosoft.com
Subject: Re: [PATCH] vmbus: retrieve connection-id from device tree
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@...nel.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
Powered by blists - more mailing lists