[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <37f0002a-a107-458b-933d-55f2cf96f5f1@linux.microsoft.com>
Date: Thu, 2 Oct 2025 16:06:51 -0700
From: Easwar Hariharan <easwar.hariharan@...ux.microsoft.com>
To: Stanislav Kinsburskii <skinsburskii@...ux.microsoft.com>
Cc: easwar.hariharan@...ux.microsoft.com, "K. Y. Srinivasan"
<kys@...rosoft.com>, Haiyang Zhang <haiyangz@...rosoft.com>,
Wei Liu <wei.liu@...nel.org>, Dexuan Cui <decui@...rosoft.com>,
Nuno Das Neves <nunodasneves@...ux.microsoft.com>,
"open list:Hyper-V/Azure CORE AND DRIVERS" <linux-hyperv@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Drivers: hv: Use -ETIMEDOUT for HV_STATUS_TIME_OUT
instead of -EIO
On 10/2/2025 3:37 PM, Stanislav Kinsburskii wrote:
> On Thu, Oct 02, 2025 at 10:13:46PM +0000, Easwar Hariharan wrote:
>> Use the -ETIMEDOUT errno value as the correct 1:1 match for the
>> hypervisor timeout status
>>
>
> The commit message should answer the question why this change is being
> made.
> Is there a practical reason for this or is it only for consistensy?
>
<snip>
It's for consistency and because it's a better match. See my sibling response
for other error codes that I can also fix in a v2.
Thanks,
Easwar (he/him)
Powered by blists - more mailing lists