From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Lee Jones <lee@kernel•org>
Cc: Robert Marko <robert.marko@sartura•hr>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build warning after merge of the mfd tree
Date: Thu, 24 Jul 2025 11:54:09 +1000 [thread overview]
Message-ID: <20250724115409.030d0d08@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 548 bytes --]
Hi all,
After merging the mfd tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
WARNING: unmet direct dependencies detected for MFD_AT91_USART
Depends on [n]: HAS_IOMEM [=y] && (ARCH_MICROCHIP || COMPILE_TEST [=n])
Selected by [y]:
- SERIAL_ATMEL [=y] && TTY [=y] && HAS_IOMEM [=y] && COMMON_CLK [=y] && (ARCH_AT91 [=y] || ARCH_LAN969X || COMPILE_TEST [=n])
Probably introduced by commit
ef37a1e24857 ("mfd: at91-usart: Make it selectable for ARCH_MICROCHIP")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-07-24 1:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 1:54 Stephen Rothwell [this message]
2025-07-24 10:03 ` linux-next: build warning after merge of the mfd tree Lee Jones
2025-07-29 1:35 ` Stephen Rothwell
2025-08-05 3:39 ` Stephen Rothwell
2025-08-05 13:19 ` Lee Jones
-- strict thread matches above, loose matches on Subject: below --
2020-07-07 2:44 Stephen Rothwell
[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=20250724115409.030d0d08@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=lee@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=robert.marko@sartura$(echo .)hr \
/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