From: Samuel Ortiz <sameo@openedhand.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: ben@simtec.co.uk, LKML <linux-kernel@vger.kernel.org>
Subject: Re: section mismatches with _sm501_register_gpio() and _sm501_gpio_register_chip()
Date: Mon, 24 Nov 2008 20:49:12 +0100 [thread overview]
Message-ID: <20081124194911.GC2604@sortiz.org> (raw)
In-Reply-To: <8bd0f97a0811202013r170c9906i15797ca953844cff@mail.gmail.com>
Hi Mike,
On Thu, Nov 20, 2008 at 11:13:31PM -0500, Mike Frysinger wrote:
> WARNING: drivers/mfd/built-in.o(.text+0x8d6): Section mismatch in
> reference from the function _sm501_register_gpio() to the function
> .devinit.text:_sm501_gpio_register_chip()
> The function _sm501_register_gpio() references
> the function __devinit _sm501_gpio_register_chip().
> This is often because _sm501_register_gpio lacks a __devinit
> annotation or the annotation of _sm501_gpio_register_chip is wrong.
>
> WARNING: drivers/mfd/built-in.o(.text+0x90a): Section mismatch in
> reference from the function _sm501_register_gpio() to the function
> .devinit.text:_sm501_gpio_register_chip()
> The function _sm501_register_gpio() references
> the function __devinit _sm501_gpio_register_chip().
> This is often because _sm501_register_gpio lacks a __devinit
> annotation or the annotation of _sm501_gpio_register_chip is wrong.
Which kernel are you triggering this on ?
Cheers,
Samuel.
> #
> # Multifunction device drivers
> #
> # CONFIG_MFD_CORE is not set
> CONFIG_MFD_SM501=y
> CONFIG_MFD_SM501_GPIO=y
> CONFIG_HTC_PASIC3=y
> CONFIG_UCB1400_CORE=m
> # CONFIG_MFD_TMIO is not set
> # CONFIG_MFD_WM8400 is not set
> CONFIG_MFD_WM8350=y
> CONFIG_MFD_WM8350_I2C=y
> -mike
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2008-11-24 19:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 4:13 section mismatches with _sm501_register_gpio() and _sm501_gpio_register_chip() Mike Frysinger
2008-11-24 19:49 ` Samuel Ortiz [this message]
2008-12-18 20:56 ` Mike Frysinger
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=20081124194911.GC2604@sortiz.org \
--to=sameo@openedhand.com \
--cc=ben@simtec.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=vapier.adi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.