public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Nathan Chancellor <natechancellor@gmail.com>
Cc: Nicolas Ferre <nicolas.ferre@microchip.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Ludovic Desroches <ludovic.desroches@microchip.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] misc: atmel-ssc: Fix section annotation on atmel_ssc_get_driver_data
Date: Wed, 17 Oct 2018 20:16:25 +0200	[thread overview]
Message-ID: <20181017181625.GW17341@piout.net> (raw)
In-Reply-To: <20181017170901.13119-1-natechancellor@gmail.com>

On 17/10/2018 10:09:02-0700, Nathan Chancellor wrote:
> After building the kernel with Clang, the following section mismatch
> warning appears:
> 
> WARNING: vmlinux.o(.text+0x3bf19a6): Section mismatch in reference from
> the function ssc_probe() to the function
> .init.text:atmel_ssc_get_driver_data()
> The function ssc_probe() references
> the function __init atmel_ssc_get_driver_data().
> This is often because ssc_probe lacks a __init
> annotation or the annotation of atmel_ssc_get_driver_data is wrong.
> 
> Remove __init from atmel_ssc_get_driver_data to get rid of the mismatch.
> 

Reviewed-by: Alexandre Belloni <alexandre.belloni@bootlin.com>

I would add:

Fixes: 5c86ac695c7e ("ASoC: atmel-ssc: use module_platform_driver macro")

> Signed-off-by: Nathan Chancellor <natechancellor@gmail.com>
> ---
> 
> Alternatively, ssc_probe could be marked as __init, I don't think there
> is any way for the probe to defer. I decided to go with the more
> conservative option first but I'm happy to respin if necessary.
> 

A probe function should never be marked __init, unless you ensure there
is no way to bind/unbind the driver at runtime.

> Thanks!
> 
>  drivers/misc/atmel-ssc.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/misc/atmel-ssc.c b/drivers/misc/atmel-ssc.c
> index b2a0340f277e..d8e3cc2dc747 100644
> --- a/drivers/misc/atmel-ssc.c
> +++ b/drivers/misc/atmel-ssc.c
> @@ -132,7 +132,7 @@ static const struct of_device_id atmel_ssc_dt_ids[] = {
>  MODULE_DEVICE_TABLE(of, atmel_ssc_dt_ids);
>  #endif
>  
> -static inline const struct atmel_ssc_platform_data * __init
> +static inline const struct atmel_ssc_platform_data *
>  	atmel_ssc_get_driver_data(struct platform_device *pdev)
>  {
>  	if (pdev->dev.of_node) {
> -- 
> 2.19.1
> 

-- 
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-10-17 18:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-17 17:09 [PATCH] misc: atmel-ssc: Fix section annotation on atmel_ssc_get_driver_data Nathan Chancellor
2018-10-17 18:16 ` Alexandre Belloni [this message]
2018-10-17 18:20   ` Nathan Chancellor
2018-10-17 18:31     ` Alexandre Belloni

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=20181017181625.GW17341@piout.net \
    --to=alexandre.belloni@bootlin.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ludovic.desroches@microchip.com \
    --cc=natechancellor@gmail.com \
    --cc=nicolas.ferre@microchip.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