[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7d96064c-1198-4de6-b0b6-1107a9ef229a@suse.com>
Date: Wed, 25 Jun 2025 17:57:25 +0300
From: Nikolay Borisov <nik.borisov@...e.com>
To: Yazen Ghannam <yazen.ghannam@....com>, x86@...nel.org,
Tony Luck <tony.luck@...el.com>, "Rafael J. Wysocki" <rafael@...nel.org>,
Len Brown <lenb@...nel.org>
Cc: linux-kernel@...r.kernel.org, linux-edac@...r.kernel.org,
Smita.KoralahalliChannabasappa@....com, Qiuxu Zhuo <qiuxu.zhuo@...el.com>,
linux-acpi@...r.kernel.org
Subject: Re: [PATCH v4 06/22] x86/mce/amd: Remove return value for
mce_threshold_{create,remove}_device()
On 6/24/25 17:16, Yazen Ghannam wrote:
> The return values are not checked, so set return type to 'void'.
>
> Also, move function declarations to internal.h, since these functions are
> only used within the MCE subsystem.
>
> Signed-off-by: Yazen Ghannam <yazen.ghannam@....com>
Realistically the only case when this code can fail is if the machine is
tight on memory and a cpu is brought on. So the wider question is should
such a situation fail the hotplug event? Likely something else in the
chain would have failed up earlier, so I guess the answer is no.
In any case LGTM:
Reviewed-by: Nikolay Borisov <nik.borisov@...e.com>
Powered by blists - more mailing lists