From: Len Brown <lenb@kernel.org>
To: Marin Mitov <mitov@issp.bas.bg>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rusty Russell <rusty@rustycorp.com.au>,
Srivatsa Vaddagiri <vatsa@in.ibm.com>,
Zwane Mwaikambo <zwane@arm.linux.org.uk>,
Ashok Raj <ashok.raj@intel.com>,
tony.luck@intel.com, Alex Chiang <achiang@hp.com>
Subject: Re: [PATCH] Section mismatch: acpi_early_processor_set_pdc()
Date: Sat, 16 Jan 2010 02:07:00 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.1001160206070.10250@localhost.localdomain> (raw)
In-Reply-To: <201001132244.49209.mitov@issp.bas.bg>
I think tony's patch (in my tree) to change this to __init is correct.
thanks,
Len Brown, Intel Open Source Technology Center
On Wed, 13 Jan 2010, Marin Mitov wrote:
> Hi all,
>
> kernel-2.6.33-rc4, compiler output:
>
> WARNING: Section mismatch in reference from the function
> acpi_early_processor_set_pdc() to the variable .cpuinit.data:processor_idle_dmi_table
> The function acpi_early_processor_set_pdc() references
> the variable __cpuinitdata processor_idle_dmi_table.
> This is often because acpi_early_processor_set_pdc lacks a __cpuinitdata
> annotation or the annotation of processor_idle_dmi_table is wrong.
>
> acpi_early_processor_set_pdc() is invoked only from __init acpi_bus_init()
> Mark it __cpuinit.
>
> The patch is against 2.6.33-rc4
>
> Signed-off-by: Marin Mitov <mitov@issp.bas.bg>
>
> ===========================================================================
> --- a/drivers/acpi/processor_pdc.c 2010-01-13 21:53:14.000000000 +0200
> +++ b/drivers/acpi/processor_pdc.c 2010-01-13 21:58:39.000000000 +0200
> @@ -151,7 +151,7 @@
> return AE_OK;
> }
>
> -void acpi_early_processor_set_pdc(void)
> +void __cpuinit acpi_early_processor_set_pdc(void)
> {
> /*
> * Check whether the system is DMI table. If yes, OSPM
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
prev parent reply other threads:[~2010-01-16 7:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 20:44 Marin Mitov
2010-01-16 7:07 ` Len Brown [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=alpine.LFD.2.00.1001160206070.10250@localhost.localdomain \
--to=lenb@kernel.org \
--cc=achiang@hp.com \
--cc=ashok.raj@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mitov@issp.bas.bg \
--cc=rusty@rustycorp.com.au \
--cc=tony.luck@intel.com \
--cc=vatsa@in.ibm.com \
--cc=zwane@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®