mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Samuel Ortiz" <sameo@openedhand.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: Thu, 18 Dec 2008 15:56:53 -0500	[thread overview]
Message-ID: <8bd0f97a0812181256j68326d28t15cf4370571b04bd@mail.gmail.com> (raw)
In-Reply-To: <20081124194911.GC2604@sortiz.org>

On Mon, Nov 24, 2008 at 14:49, Samuel Ortiz wrote:
> 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 ?

sorry, i missed this response ... this was in 2.6.28-rc2
-mike

      reply	other threads:[~2008-12-18 20:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-21  4:13 Mike Frysinger
2008-11-24 19:49 ` Samuel Ortiz
2008-12-18 20:56   ` Mike Frysinger [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=8bd0f97a0812181256j68326d28t15cf4370571b04bd@mail.gmail.com \
    --to=vapier.adi@gmail.com \
    --cc=ben@simtec.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sameo@openedhand.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

all inboxes | Powered by JetHome®