public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Qiao Zhou <zhouqiao@marvell.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: SamuelOrtiz <sameo@linux.intel.com>,
	Arnd Bergmann <arnd@arndb.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mfd: Remove __devexit annotation for pm80x_deinit
Date: Wed, 11 Jul 2012 09:52:20 +0800	[thread overview]
Message-ID: <4FFCDC54.8030408@marvell.com> (raw)
In-Reply-To: <1341971280.25495.0.camel@phoenix>

On 07/11/2012 09:48 AM, Axel Lin wrote:
> This fixes below section mismatch warning:
>
>    LD      drivers/mfd/built-in.o
> WARNING: drivers/mfd/built-in.o(.devinit.text+0x46c): Section mismatch in reference from the function pm800_probe() to the function .devexit.text:pm80x_deinit()
> The function __devinit pm800_probe() references
> a function __devexit pm80x_deinit().
> This is often seen when error handling in the init function
> uses functionality in the exit path.
> The fix is often to remove the __devexit annotation of
> pm80x_deinit() so it may be used outside an exit section.
>
> Signed-off-by: Axel Lin <axel.lin@gmail.com>
> ---
>   drivers/mfd/88pm80x.c |    2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mfd/88pm80x.c b/drivers/mfd/88pm80x.c
> index 62da342..cd0bf52 100644
> --- a/drivers/mfd/88pm80x.c
> +++ b/drivers/mfd/88pm80x.c
> @@ -91,7 +91,7 @@ err_regmap_init:
>   }
>   EXPORT_SYMBOL_GPL(pm80x_init);
>
> -int __devexit pm80x_deinit(struct i2c_client *client)
> +int pm80x_deinit(struct i2c_client *client)
>   {
>   	struct pm80x_chip *chip = i2c_get_clientdata(client);
>
>
Alex,

thanks again for the fixing, and would try to avoid such warning in future.

-- 

Best Regards
Qiao



      reply	other threads:[~2012-07-11  1:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-11  1:48 [PATCH] mfd: Remove __devexit annotation for pm80x_deinit Axel Lin
2012-07-11  1:52 ` Qiao Zhou [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=4FFCDC54.8030408@marvell.com \
    --to=zhouqiao@marvell.com \
    --cc=arnd@arndb.de \
    --cc=axel.lin@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sameo@linux.intel.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