From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>, <linux-iio@vger.kernel.org>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] iio: mma8452: Fix 'mma8452_dt_ids' defined but not used compiler warning
Date: Mon, 14 Feb 2022 10:54:56 +0000 [thread overview]
Message-ID: <20220214105456.00002177@Huawei.com> (raw)
In-Reply-To: <20220214091850.44139-1-hdegoede@redhat.com>
On Mon, 14 Feb 2022 10:18:50 +0100
Hans de Goede <hdegoede@redhat.com> wrote:
> Commit 90adc57bd55a ("iio: mma8452: Fix probe failing when an
> i2c_device_id is used") introduces a new: "'mma8452_dt_ids' defined
> but not used" compiler warning.
>
> This is caused by the switch from of_match_device() (which takes a
> pointer to this) to device_get_match_data(), combined with the use of
> of_match_ptr() when setting of_match_table.
>
> We actually want mma8452_dt_ids to get optmized away when CONFIG_OF is
> not set, so mark it as __maybe_unused to silence the warning.
>
> Fixes: 90adc57bd55a ("iio: mma8452: Fix probe failing when an i2c_device_id is used")
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
For this I'd rather drop the of_match_ptr() protection.
We will need to do that anyway shortly as part of converting this
to fully device properties and allowing ACPI PRP0001 which uses
the of_match_table from ACPI.
We can now easily make that transition as (via Andy)
https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git/commit/?h=i2c/alert-for-acpi&id=ca0acb511c21738b32386ce0f85c284b351d919e
Anyhow, I can just fix it up on the original patch once I'm on the
right computer. I might also post patches to get rid
of the of dependency completely if no one else gets there
before me.
Thanks,
Jonathan
> ---
> Note the 90adc57bd55a hash is from the jic23/iio.git testing branch, not
> sure of it is stable. It is probably best to just squash this into the
> original commit.
> ---
> drivers/iio/accel/mma8452.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/iio/accel/mma8452.c b/drivers/iio/accel/mma8452.c
> index 590d9431e1bd..1324bd515377 100644
> --- a/drivers/iio/accel/mma8452.c
> +++ b/drivers/iio/accel/mma8452.c
> @@ -1529,7 +1529,7 @@ static int mma8452_reset(struct i2c_client *client)
> return -ETIMEDOUT;
> }
>
> -static const struct of_device_id mma8452_dt_ids[] = {
> +static const struct of_device_id __maybe_unused mma8452_dt_ids[] = {
> { .compatible = "fsl,mma8451", .data = &mma_chip_info_table[mma8451] },
> { .compatible = "fsl,mma8452", .data = &mma_chip_info_table[mma8452] },
> { .compatible = "fsl,mma8453", .data = &mma_chip_info_table[mma8453] },
next prev parent reply other threads:[~2022-02-14 11:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 9:18 [PATCH] iio: mma8452: Fix 'mma8452_dt_ids' defined but not used compiler warning Hans de Goede
2022-02-14 10:54 ` Jonathan Cameron [this message]
2022-02-14 10:59 ` Hans de Goede
2022-02-18 11:30 ` Jonathan Cameron
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=20220214105456.00002177@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=hdegoede@redhat.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=lkp@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