From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: linux-next: build failure after merge of the pm tree (Was: linux-next: build warning after merge of the pm tree)
Date: Tue, 15 Oct 2019 10:16:50 +1100 [thread overview]
Message-ID: <20191015101650.2a1541af@canb.auug.org.au> (raw)
In-Reply-To: <20191015100855.31b8a3d5@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1436 bytes --]
Hi all,
On Tue, 15 Oct 2019 10:08:55 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> After merging the pm tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> In file included from include/linux/irqchip.h:14,
> from arch/arm/kernel/irq.c:26:
> include/linux/acpi.h:682:31: warning: 'struct acpi_device' declared inside parameter list will not be visible outside of this definition or declaration
> 682 | acpi_dev_hid_uid_match(struct acpi_device *adev, const char *hid2, const char *uid2)
> | ^~~~~~~~~~~
>
> and many more.
>
> Introduced by commit
>
> d1748b57dc88 ("ACPI / utils: Introduce acpi_dev_hid_uid_match() helper")
>
> CONFIG_ACPI is not set for this build.
This became a build failure for the powerpc ppc64_allmodconfig build:
In file included from include/linux/i2c.h:13,
from arch/powerpc/platforms/pasemi/misc.c:14:
include/linux/acpi.h:682:31: error: 'struct acpi_device' declared inside parameter list will not be visible outside of this definition or declaration [-Werror]
682 | acpi_dev_hid_uid_match(struct acpi_device *adev, const char *hid2, const char *uid2)
| ^~~~~~~~~~~
cc1: all warnings being treated as errors
(and many more)
I have used the pm tree from next-20191014 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-10-14 23:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 23:08 linux-next: build warning after merge of the pm tree Stephen Rothwell
2019-10-14 23:16 ` Stephen Rothwell [this message]
2019-10-15 10:04 ` linux-next: build failure after merge of the pm tree (Was: linux-next: build warning after merge of the pm tree) Rafael J. Wysocki
2019-10-16 9:15 ` Geert Uytterhoeven
2019-10-16 9:33 ` Andy Shevchenko
2019-10-15 8:23 ` linux-next: build warning after merge of the pm tree Andy Shevchenko
2019-10-15 9:41 ` Rafael J. Wysocki
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=20191015101650.2a1541af@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
/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;
as well as URLs for NNTP newsgroup(s).