Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Daniel Palmer <daniel@0x0f.com>
Cc: lars@metafoo.de, linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: accel: mma7660: Mark acpi match table as maybe unused
Date: Sun, 19 Sep 2021 17:03:30 +0100	[thread overview]
Message-ID: <20210919170330.0b79cb0e@jic23-huawei> (raw)
In-Reply-To: <20210919072616.3849723-1-daniel@0x0f.com>

On Sun, 19 Sep 2021 16:26:16 +0900
Daniel Palmer <daniel@0x0f.com> wrote:

> When building kernels without ACPI support the table is declared
> but is not used because ACPI_PTR() turns it into a NULL.
> 
> Add the __maybe_unused attribute to stop the compiler whining.
> 
> Signed-off-by: Daniel Palmer <daniel@0x0f.com>
Applied to the togreg branch of iio.git which is initially pushed out as testing
to let 0-day poke at it and see if we missed anything.

Thanks,

Jonathan

> ---
>  drivers/iio/accel/mma7660.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/iio/accel/mma7660.c b/drivers/iio/accel/mma7660.c
> index 47f5cd66e996..cd6cdf2c51b0 100644
> --- a/drivers/iio/accel/mma7660.c
> +++ b/drivers/iio/accel/mma7660.c
> @@ -254,7 +254,7 @@ static const struct of_device_id mma7660_of_match[] = {
>  };
>  MODULE_DEVICE_TABLE(of, mma7660_of_match);
>  
> -static const struct acpi_device_id mma7660_acpi_id[] = {
> +static const struct acpi_device_id __maybe_unused mma7660_acpi_id[] = {
>  	{"MMA7660", 0},
>  	{}
>  };


      reply	other threads:[~2021-09-19 15:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-19  7:26 [PATCH] iio: accel: mma7660: Mark acpi match table as maybe unused Daniel Palmer
2021-09-19 16:03 ` Jonathan Cameron [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=20210919170330.0b79cb0e@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=daniel@0x0f.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox