From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Lee Jones <lee@kernel.org>
Cc: "Duje Mihanović" <duje.mihanovic@skole.hr>,
"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 backlight tree
Date: Mon, 26 Feb 2024 13:28:28 +1100 [thread overview]
Message-ID: <20240226132828.7524baec@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 509 bytes --]
Hi all,
After merging the backlight tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/video/backlight/ktd2801-backlight.c:8:10: fatal error: linux/leds-expresswire.h: No such file or directory
8 | #include <linux/leds-expresswire.h>
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
Caused by commit
48749e2f14e3 ("backlight: Add Kinetic KTD2801 backlight support")
I have used the backlight tree from next-20240223 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-02-26 2:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 2:28 Stephen Rothwell [this message]
2024-03-05 0:16 ` linux-next: build failure after merge of the backlight tree Stephen Rothwell
2024-03-05 9:17 ` Lee Jones
2024-03-05 22:55 ` Stephen Rothwell
2024-03-06 3:04 ` Stephen Rothwell
2024-03-07 8:24 ` Lee Jones
2024-03-07 9:04 ` Lee Jones
2024-03-07 19:30 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2015-05-27 3:11 Stephen Rothwell
2015-05-27 7:45 ` Lee Jones
2010-05-10 2:43 Stephen Rothwell
2010-05-10 5:41 ` Mike Frysinger
2010-05-17 3:32 ` Stephen Rothwell
2010-05-18 15:54 ` Richard Purdie
2010-05-19 0:56 ` 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=20240226132828.7524baec@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=duje.mihanovic@skole.hr \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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