From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Lee Jones <lee@kernel•org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build failure after merge of the leds-lj tree
Date: Fri, 21 Mar 2025 15:52:01 +1100 [thread overview]
Message-ID: <20250321155201.633e8aed@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 365 bytes --]
Hi all,
After merging the leds-lj tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/leds/Kconfig:1027: can't open file "drivers/leds/simple/Kconfig"
Caused by commit
f33c17919d44 ("leds: Rename simple directory to simatic")
I have used the leds-lj tree from next-20250320 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-03-21 4:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 4:52 Stephen Rothwell [this message]
2025-03-21 9:24 ` linux-next: build failure after merge of the leds-lj tree Lee Jones
-- strict thread matches above, loose matches on Subject: below --
2026-03-06 13:47 Mark Brown
2026-01-09 1:45 Stephen Rothwell
2026-01-09 9:41 ` Lee Jones
2026-01-19 18:56 ` Mark Brown
2026-01-20 8:46 ` Lee Jones
2026-01-26 22:00 ` Mark Brown
2026-02-02 14:56 ` Mark Brown
2026-02-03 18:26 ` Mark Brown
2026-02-04 9:21 ` Lee Jones
2025-02-21 3:42 Stephen Rothwell
2024-07-12 4:48 Stephen Rothwell
2024-07-12 7:31 ` Lee Jones
2024-07-12 7:48 ` Christian Marangi
2024-07-12 8:21 ` Lee Jones
2024-07-10 6:34 Stephen Rothwell
2024-07-10 7:16 ` Lee Jones
2024-01-29 2:10 Stephen Rothwell
2024-01-31 8:56 ` Lee Jones
[not found] <20230809131733.67238c8a@canb.auug.org.au>
2023-08-09 12:53 ` Marek Vasut
2023-03-20 0:48 Stephen Rothwell
2023-03-20 1:00 ` ChiYuan Huang
2023-03-21 23:55 ` Stephen Rothwell
2023-03-22 15:28 ` Lee Jones
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=20250321155201.633e8aed@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 \
/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