From: Guenter Roeck <linux@roeck-us.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrej Picej <andpicej@gmail.com>
Subject: Re: linux-next: build failure after merge of the hwmon-staging tree
Date: Tue, 28 Apr 2020 06:19:12 -0700 [thread overview]
Message-ID: <9ff86023-9ee1-23d8-1d84-4bb7b984d6a1@roeck-us.net> (raw)
In-Reply-To: <20200428163655.28eeeae0@canb.auug.org.au>
[-- Attachment #1.1: Type: text/plain, Size: 785 bytes --]
On 4/27/20 11:36 PM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the hwmon-staging tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/hwmon/lm70.c: In function 'lm70_probe':
> drivers/hwmon/lm70.c:186:34: error: 'lm70_acpi_ids' undeclared (first use in this function); did you mean 'lm70_of_ids'?
> 186 | acpi_match = acpi_match_device(lm70_acpi_ids, &spi->dev);
> | ^~~~~~~~~~~~~
> | lm70_of_ids
>
> Caused by commit
>
> 02b925a9104d ("hwmon: (lm70) Add support for ACPI")
>
> CONFIG_ACPI is not set.
>
> I have reverted that commit for today.
>
I fixed it up. And I'll have to add test builds with CONFIG_ACPI=n.
Guenter
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-04-28 13:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 6:36 linux-next: build failure after merge of the hwmon-staging tree Stephen Rothwell
2020-04-28 13:19 ` Guenter Roeck [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-27 5:41 Stephen Rothwell
2023-01-24 22:24 Stephen Rothwell
2023-01-24 22:27 ` Guenter Roeck
2022-08-30 23:30 Stephen Rothwell
2022-08-31 12:03 ` Michael Shych
2022-05-10 12:26 Stephen Rothwell
2020-10-01 2:53 Stephen Rothwell
2020-10-01 15:09 ` Guenter Roeck
2020-08-24 0:28 Stephen Rothwell
2020-08-24 7:01 ` Guenter Roeck
2020-03-22 23:37 Stephen Rothwell
2020-03-22 23:45 ` Guenter Roeck
2019-02-25 23:55 Stephen Rothwell
2019-02-26 0:11 ` Guenter Roeck
2018-12-16 23:00 Stephen Rothwell
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=9ff86023-9ee1-23d8-1d84-4bb7b984d6a1@roeck-us.net \
--to=linux@roeck-us.net \
--cc=andpicej@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).