From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Lee Jones <lee.jones@linaro•org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: linux-next: build warning after merge of the mfd tree
Date: Tue, 7 Jul 2020 12:44:31 +1000 [thread overview]
Message-ID: <20200707124431.450bb0da@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 415 bytes --]
Hi all,
After merging the mfd tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
drivers/mfd/axp20x-i2c.c:82:5: warning: "CONFIG_ACPI" is not defined, evaluates to 0 [-Wundef]
82 | #if CONFIG_ACPI
| ^~~~~~~~~~~
Introduced by commit
20f359cb236b ("mfd: axp20x-i2c: Do not define 'struct acpi_device_id' when !CONFIG_ACPI")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-07-07 2:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 2:44 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-24 1:54 linux-next: build warning after merge of the mfd tree Stephen Rothwell
2025-07-24 10:03 ` Lee Jones
2025-07-29 1:35 ` Stephen Rothwell
2025-08-05 3:39 ` Stephen Rothwell
2025-08-05 13:19 ` Lee Jones
[not found] <20190627151140.232a87e2@canb.auug.org.au>
2019-06-27 5:59 ` Keerthy
2019-07-02 8:49 ` Stephen Rothwell
2019-07-02 11:09 ` Lee Jones
2018-06-05 3:15 Stephen Rothwell
2018-06-05 6:55 ` Lee Jones
2017-11-30 0:35 Stephen Rothwell
2017-11-30 8:28 ` Lee Jones
2017-01-25 4:54 Stephen Rothwell
2017-01-25 8:13 ` Benjamin Gaignard
2013-07-03 5:56 Stephen Rothwell
2013-07-07 18:29 ` Sebastian Andrzej Siewior
2011-12-20 3:11 Stephen Rothwell
2010-11-29 0:52 Stephen Rothwell
2010-11-30 10:02 ` Samuel Ortiz
2010-03-03 5:22 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=20200707124431.450bb0da@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=lee.jones@linaro$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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