[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <83070bd2-209a-4143-9efa-0a67f489563f@linux.microsoft.com>
Date: Wed, 30 Jul 2025 16:38:33 +0530
From: Naman Jain <namjain@...ux.microsoft.com>
To: Abhishek Tiwari <abhitiwari@...ux.microsoft.com>,
abhitiwari@...rosoft.com, kys@...rosoft.com, haiyangz@...rosoft.com,
wei.liu@...nel.org, decui@...rosoft.com, linux-hyperv@...r.kernel.org,
linux-kernel@...r.kernel.org, ssengar@...rosoft.com
Subject: Re: [PATCH] x86/hyperv: Cosmetic changes for hv_utils_transport.c
On 7/30/2025 4:07 PM, Abhishek Tiwari wrote:
> Fix issues reported by checkpatch.pl script for hv_utils_transport.c file
> - Update pr_warn() calls to use __func__ for consistent logging context.
> - else should follow close brace '}'
>
> No functional changes intended.
>
> Signed-off-by: Abhishek Tiwari <abhitiwari@...ux.microsoft.com>
Please use a different prefix for Subject.
Replace "x86/hyperv:" with "Drivers: hv: util:"
We generally follow the naming practice used for a file, which can be
seen in git log <file_path>.
Rest LGTM. Post above change:
Reviewed-by: Naman Jain <namjain@...ux.microsoft.com>
Regards,
Naman
Powered by blists - more mailing lists