All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Jean Delvare <jdelvare@suse.com>,
	linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon: (iio_hwmon) Drop bogus __refdata annotation
Date: Fri, 11 Dec 2020 07:26:46 -0800	[thread overview]
Message-ID: <20201211152646.GA39888@roeck-us.net> (raw)
In-Reply-To: <20201211133512.2969952-1-geert+renesas@glider.be>

On Fri, Dec 11, 2020 at 02:35:12PM +0100, Geert Uytterhoeven wrote:
> As the IIO hardware monitoring driver does not have any code or data
> located in initmem, there is no need to annotate the iio_hwmon_driver
> structure with __refdata.  Drop the annotation, to avoid suppressing
> future section warnings.
> 
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>

Applied.

Thanks,
Guenter

> ---
>  drivers/hwmon/iio_hwmon.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/hwmon/iio_hwmon.c b/drivers/hwmon/iio_hwmon.c
> index b85a125dd86f46a2..580a7d125b88667b 100644
> --- a/drivers/hwmon/iio_hwmon.c
> +++ b/drivers/hwmon/iio_hwmon.c
> @@ -169,7 +169,7 @@ static const struct of_device_id iio_hwmon_of_match[] = {
>  };
>  MODULE_DEVICE_TABLE(of, iio_hwmon_of_match);
>  
> -static struct platform_driver __refdata iio_hwmon_driver = {
> +static struct platform_driver iio_hwmon_driver = {
>  	.driver = {
>  		.name = "iio_hwmon",
>  		.of_match_table = iio_hwmon_of_match,

      reply	other threads:[~2020-12-11 16:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-11 13:35 [PATCH] hwmon: (iio_hwmon) Drop bogus __refdata annotation Geert Uytterhoeven
2020-12-11 15:26 ` Guenter Roeck [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=20201211152646.GA39888@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=geert+renesas@glider.be \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 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.