From: Lee Jones <lee@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the leds-lj tree
Date: Fri, 21 Mar 2025 09:24:46 +0000 [thread overview]
Message-ID: <20250321092446.GF1750245@google.com> (raw)
In-Reply-To: <20250321155201.633e8aed@canb.auug.org.au>
On Fri, 21 Mar 2025, Stephen Rothwell wrote:
> 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.
Thanks. This has been fixed in:
https://web.git.kernel.org/pub/scm/linux/kernel/git/lee/leds.git/commit/?h=for-leds-next&id=835a0c10d33b54607f49edffbbeaea4c4cdcc49c
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2025-03-21 9:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 4:52 linux-next: build failure after merge of the leds-lj tree Stephen Rothwell
2025-03-21 9:24 ` Lee Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
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=20250321092446.GF1750245@google.com \
--to=lee@kernel.org \
--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).