public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Steffen Trumtrar <s.trumtrar@pengutronix.de>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	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, 4 Feb 2026 09:21:07 +0000	[thread overview]
Message-ID: <20260204092107.GA911837@google.com> (raw)
In-Reply-To: <3cd56914-a83d-468f-9a1c-76c24cfd2c5e@sirena.org.uk>

On Tue, 03 Feb 2026, Mark Brown wrote:

> On Mon, Feb 02, 2026 at 02:56:27PM +0000, Mark Brown wrote:
> > On Fri, Jan 09, 2026 at 12:45:58PM +1100, Stephen Rothwell wrote:
> > > Hi all,
> > > 
> > > After merging the leds-lj tree, today's linux-next build (x86_64
> > > allmodconfig) failed like this:
> > 
> > This issue is still present in today's -next, the leds-lj tree is still
> > using the version from 8th January.
> 
> This means that these commits have never been in -next and we're at -rc8
> now:
> 
> Daniel Mack (3):
>       dt-bindings: leds: Add issi,is31fl3293 to leds-is31fl32xx
>       leds: is31f132xx: Re-order code to remove forward declarations
>       leds: is31f132xx: Add support for is31fl3293
> 
> Nam Tran (3):
>       dt-bindings: leds: add TI/National Semiconductor LP5812 LED Driver
>       leds: Add basic support for TI/National Semiconductor LP5812 LED Driver
>       docs: leds: Document TI LP5812 LED driver
> 
> Steffen Trumtrar (3):
>       dt-bindings: leds: Add LP5860 LED controller
>       leds: Add support for TI LP5860 LED driver chip
>       leds: lp5860: Fix unused-but-set-variable warning
> 
> Jishnu Prakash (2):
>       dt-bindings: leds: leds-qcom-lpg: Add support for PMH0101 PWM
>       dt-bindings: leds: qcom,spmi-flash-led: Add PMH0101 compatible
> 
> Lukas Timmermann (2):
>       dt-bindings: leds: Add new as3668 support
>       leds: as3668: Driver for the ams Osram 4-channel i2c LED driver
> 
> Duje Mihanović (1):
>       leds: expresswire: Fix chip state breakage
> 
> Haotian Zhang (1):
>       leds: qcom-lpg: Check the return value of regmap_bulk_write()
> 
> J. Neuschäfer (1):
>       dt-bindings: leds: Allow differently named multicolor LEDs
> 
> Krzysztof Kozlowski (1):
>       leds: lp55xx: Simplify with scoped for each OF child loop
> 
> Vivek BalachandharTN (1):
>       leds: lm3692x: Fix kernel-doc for struct lm3692x_led
> 
> The leds-lj tree in -next currently contains only:
> 
> Lukas Timmermann (2):
>       dt-bindings: leds: Add new as3668 support
>       leds: as3668: Driver for the ams Osram 4-channel i2c LED driver

Apologies, I was on vacation all last week.

I have removed the offending commit.

-- 
Lee Jones [李琼斯]

  reply	other threads:[~2026-02-04  9:21 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
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 [this message]
  -- 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=20260204092107.GA911837@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