From: Zhang Rui <rui.zhang@intel.com>
To: Namhyung Kim <namhyung@gmail.com>
Cc: Len Brown <lenb@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ACPI: fix section mismatch warning
Date: Thu, 09 Dec 2010 13:05:15 +0800 [thread overview]
Message-ID: <1291871115.1715.116.camel@rui> (raw)
In-Reply-To: <1291865712-31557-1-git-send-email-namhyung@gmail.com>
On Thu, 2010-12-09 at 11:35 +0800, Namhyung Kim wrote:
> Annotate acpi_os_initialize1() as __init to fix following warning:
>
> LD vmlinux.o
> MODPOST vmlinux.o
> WARNING: vmlinux.o(.text+0x231587): Section mismatch in reference from the function
> acpi_os_initialize1() to the function .init.text:acpi_osi_setup_late()
> The function acpi_os_initialize1() references
> the function __init acpi_osi_setup_late().
> This is often because acpi_os_initialize1 lacks a __init
> annotation or the annotation of acpi_osi_setup_late is wrong.
>
> Signed-off-by: Namhyung Kim <namhyung@gmail.com>
yes, this is the same patch as
https://patchwork.kernel.org/patch/389432/
thanks,
rui
> ---
> drivers/acpi/osl.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/acpi/osl.c b/drivers/acpi/osl.c
> index 966feddf6b1b..f7227e990b0f 100644
> --- a/drivers/acpi/osl.c
> +++ b/drivers/acpi/osl.c
> @@ -1530,7 +1530,7 @@ acpi_status __init acpi_os_initialize(void)
> return AE_OK;
> }
>
> -acpi_status acpi_os_initialize1(void)
> +acpi_status __init acpi_os_initialize1(void)
> {
> kacpid_wq = create_workqueue("kacpid");
> kacpi_notify_wq = create_workqueue("kacpi_notify");
prev parent reply other threads:[~2010-12-09 5:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 3:35 [PATCH] ACPI: fix section mismatch warning Namhyung Kim
2010-12-09 5:05 ` Zhang Rui [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1291871115.1715.116.camel@rui \
--to=rui.zhang@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox