public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Gwendal Grignou <gwendal@chromium.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the iio tree
Date: Thu, 9 Feb 2023 10:20:07 +0000	[thread overview]
Message-ID: <20230209102007.00002d07@Huawei.com> (raw)
In-Reply-To: <20230209143821.7e6870e8@canb.auug.org.au>

On Thu, 9 Feb 2023 14:38:21 +1100
Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi all,
> 
> After merging the iio tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
> 
> drivers/iio/proximity/sx_common.c: In function 'sx_common_get_raw_register_config':
> drivers/iio/proximity/sx_common.c:438:55: error: implicit declaration of function 'acpi_device_hid'; did you mean 'dmi_device_id'? [-Werror=implicit-function-declaration]
>   438 |         snprintf(prop, ARRAY_SIZE(prop), "%s,reg_%s", acpi_device_hid(adev), reg_def->property);
>       |                                                       ^~~~~~~~~~~~~~~
>       |                                                       dmi_device_id
> drivers/iio/proximity/sx_common.c:438:44: error: format '%s' expects argument of type 'char *', but argument 4 has type 'int' [-Werror=format=]
>   438 |         snprintf(prop, ARRAY_SIZE(prop), "%s,reg_%s", acpi_device_hid(adev), reg_def->property);
>       |                                           ~^          ~~~~~~~~~~~~~~~~~~~~~
>       |                                            |          |
>       |                                            char *     int
>       |                                           %d
> cc1: all warnings being treated as errors
> 
> Caused by commit
> 
>   91af1d6c497b ("iio: proximity: sx_common: Add old register mapping")
> 
> I have reverted that commit for today.
> 

Thanks,  I misdiagnosed the issue in previous attempt to fix this.
Problem is lack of stub for that function in !CONFIG_ACPI
(not as I thought a missing include - which was also the case).

As that will need an ACPI related header change to avoid ifdef nastiness
in the driver I'll drop the patch from my tree and we can get back
to this next cycle.

Thanks again,

Jonathan
 



  reply	other threads:[~2023-02-09 10:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-09  3:38 linux-next: build failure after merge of the iio tree Stephen Rothwell
2023-02-09 10:20 ` Jonathan Cameron [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-08  4:41 Stephen Rothwell
2024-10-11  4:42 Stephen Rothwell
2024-10-11  9:42 ` Jonathan Cameron
2024-10-11 12:09   ` Greg KH
2026-01-19 19:20 Mark Brown
2026-01-20  9:47 ` 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=20230209102007.00002d07@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=gwendal@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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