From: Lee Jones <lee@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Steffen Trumtrar <s.trumtrar@pengutronix.de>,
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: Tue, 20 Jan 2026 08:46:00 +0000 [thread overview]
Message-ID: <20260120084600.GA1354723@google.com> (raw)
In-Reply-To: <9a44bf97-4c51-49b6-bdec-2959780ff128@sirena.org.uk>
On Mon, 19 Jan 2026, Mark Brown wrote:
> On Fri, Jan 09, 2026 at 09:41:47AM +0000, Lee Jones wrote:
> > On Fri, 09 Jan 2026, Stephen Rothwell wrote:
>
> > > ERROR: modpost: missing MODULE_LICENSE() in drivers/leds/rgb/leds-lp5860-core.o
> > > WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/leds/rgb/leds-lp5860-core.o
> > > ERROR: modpost: "lp5860_device_init" [drivers/leds/rgb/leds-lp5860-spi.ko] undefined!
> > > ERROR: modpost: "lp5860_device_remove" [drivers/leds/rgb/leds-lp5860-spi.ko] undefined!
>
> > > Caused by commit
>
> > > 51f7560294c9 ("leds: Add support for TI LP5860 LED driver chip")
>
> > > I have used the led-lj tree from next-20160108 for today.
>
> > Please provide a follow-up patch post-haste.
>
> This issue is still present in today's -next.
Steffen,
Please provide a follow-up or I'll have to remove your patch.
This is blocking testing.
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2026-01-20 8:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 1:45 linux-next: build failure after merge of the leds-lj tree Stephen Rothwell
2026-01-09 9:41 ` Lee Jones
2026-01-19 18:56 ` Mark Brown
2026-01-20 8:46 ` Lee Jones [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2026-03-06 13:47 Mark Brown
2025-03-21 4:52 Stephen Rothwell
2025-03-21 9:24 ` 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=20260120084600.GA1354723@google.com \
--to=lee@kernel.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=s.trumtrar@pengutronix.de \
--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