From: Lee Jones <lee@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Anjelique Melendez <quic_amelende@quicinc.com>,
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: Wed, 31 Jan 2024 08:56:54 +0000 [thread overview]
Message-ID: <20240131085654.GE8551@google.com> (raw)
In-Reply-To: <20240129131054.14bc453e@canb.auug.org.au>
On Mon, 29 Jan 2024, Stephen Rothwell wrote:
> Hi all,
>
> After merging the leds-lj tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/leds/rgb/leds-qcom-lpg.c:17:10: fatal error: linux/soc/qcom/qcom-pbs.h: No such file or directory
> 17 | #include <linux/soc/qcom/qcom-pbs.h>
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Caused by commit
>
> 8148c8234e10 ("leds: rgb: leds-qcom-lpg: Add support for PPG through single SDAM")
I'm holding out for a little while:
https://lore.kernel.org/r/20240125130432.GG74950@google.com
> I have used the leds-lj tree from next-20240125 for today.
Thanks. Please keep doing this for "a little while". :)
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2024-01-31 8:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 2:10 linux-next: build failure after merge of the leds-lj tree Stephen Rothwell
2024-01-31 8:56 ` Lee Jones [this message]
[not found] <20230809131733.67238c8a@canb.auug.org.au>
2023-08-09 12:53 ` Marek Vasut
-- strict thread matches above, loose matches on Subject: below --
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=20240131085654.GE8551@google.com \
--to=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=quic_amelende@quicinc.com \
--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).