[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <988fa24c-76d2-1c9d-9761-b356efb0576c@huawei.com>
Date: Tue, 12 Oct 2021 15:03:29 +0800
From: Hanjun Guo <guohanjun@...wei.com>
To: Arnd Bergmann <arnd@...nel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
Sudeep Holla <sudeep.holla@....com>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Len Brown <lenb@...nel.org>
CC: Arnd Bergmann <arnd@...db.de>,
Catalin Marinas <catalin.marinas@....com>,
Marc Zyngier <maz@...nel.org>, <linux-acpi@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] acpi: arm64: fix section mismatch warning
Hi Arnd,
On 2021/9/27 22:19, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@...db.de>
>
> In a gcc-11 randconfig build I came across this warning:
>
> WARNING: modpost: vmlinux.o(.text.unlikely+0x2c084): Section mismatch in reference from the function next_platform_timer() to the variable .init.data:acpi_gtdt_desc
> The function next_platform_timer() references
> the variable __initdata acpi_gtdt_desc.
> This is often because next_platform_timer lacks a __initdata
> annotation or the annotation of acpi_gtdt_desc is wrong.
>
> This happens when next_platform_timer() fails to get inlined
> despite the inline annotation. Adding '__init' solves the issue,
> and it seems best to remove the 'inline' in the process seems
> better anyway.
There was a patch to fix this issue as well [1],
but not merged yet.
[1]:
https://lore.kernel.org/linux-acpi/7f29a149-e005-f13f-2cc4-a9eb737107e1@huawei.com/T/
Thanks
Hanjun
Powered by blists - more mailing lists