From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] omap2+: pm: Fix section mismatch in pm_dbg_init()
Date: Mon, 20 Jun 2011 22:16:55 +0100 [thread overview]
Message-ID: <20110620211655.GN2082@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <87tybk6wh8.fsf@ti.com>
On Mon, Jun 20, 2011 at 02:09:39PM -0700, Kevin Hilman wrote:
> Sanjeev Premi <premi@ti.com> writes:
>
> > Fix the section mismatch warning:
> >
> > WARNING: vmlinux.o(.text+0x21118): Section mismatch
> > in reference from the function pm_dbg_init() to the
> > function .init.text:pwrdms_setup()
> > The function pm_dbg_init() references
> > the function __init pwrdms_setup().
> > This is often because pm_dbg_init lacks a __init
> > annotation or the annotation of pwrdms_setup is wrong.
> >
> > Signed-off-by: Sanjeev Premi <premi@ti.com>
> > ---
> > Applies to current linux-omap master
>
> A previous commit just removed the __init annotation here because of a
> different conflict with the regset init. The regset code is now
> removed in my queue for 3.1, so this patch is fine on top of that
> series.
>
> Queueing for v3.1 (branch: for_3.1/pm-misc)
Sigh. Please put some thought into it first and stop applying patches
without first doing some analysis and test-buliding the thing. Otherwise
you're going to be applying patches for ever which add and delete
these things.
If you make pm_dbg_init() __init, then you also have to make
pm_dbg_regset_init() __init too. What about the callers to
pm_dbg_regset_init() - are these marked __init or not? If not,
they too will have to be marked __init, etc.
If that's not possible, then the __init attribute must be deleted
from pwrdms_setup().
next prev parent reply other threads:[~2011-06-20 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 20:31 [PATCH] omap2+: pm: Fix section mismatch in pm_dbg_init() Sanjeev Premi
2011-06-20 21:09 ` Kevin Hilman
2011-06-20 21:16 ` Russell King - ARM Linux [this message]
2011-06-20 22:18 ` Kevin Hilman
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=20110620211655.GN2082@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/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