Re: [RESEND PATCH 2/2] rtc: cmos: Honor explicit use_acpi_alarm parameter value

[Gregory Price <gourry@gourry.net>]

On Thu, Oct 15, 2026 at 05:36:16PM +0000, sashiko-bot@kernel.org wrote:
> > +static bool use_acpi_alarm_explicit;
> > +
> > +static int set_use_acpi_alarm(const char *val, const struct kernel_param *kp)
> > +{
> > +	int ret;
> > +
> > +	ret = param_set_bool(val, kp);
> > +	if (!ret)
> > +		use_acpi_alarm_explicit = true;
> 
> [Severity: Low]
> Will this trigger a -Wunused-but-set-variable compiler warning on non-x86
> architectures?
> 
> The file-scoped variable use_acpi_alarm_explicit is declared and unconditionally
> assigned here, but it appears to only be read inside use_acpi_alarm_quirks(),
> which is wrapped in an #ifdef CONFIG_X86 block.
> 
> On architectures like ARM64 or PowerPC, the variable is written to but never
> read.
> 

I could not get this to trigger. Neither gcc nor clang would fire this
warning for a file-scoped static.

~Gregory