From: Lee Jones <lee@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Pavel Machek <pavel@ucw.cz>,
Lee Jones <lee@kernel.org>, Mark Brown <broonie@kernel.org>
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org
Subject: Re: [PATCH 0/4] leds: Convert to use maple tree register cache
Date: Thu, 05 Oct 2023 12:10:42 +0100 [thread overview]
Message-ID: <169650424265.688682.2460798715972634009.b4-ty@kernel.org> (raw)
In-Reply-To: <20230929-leds-maple-v1-0-ba5f9dcb1e75@kernel.org>
On Fri, 29 Sep 2023 17:23:34 +0200, Mark Brown wrote:
> The maple tree register cache is a more modern replacement for the
> rbtree cache, the underlying data structure is more modern and the
> surrounding cache implementation makes a number of choices which are
> more suited to modern systems than those made by rbtree. This series
> updates the LED drivers that use the rbtree cache to use the maple tree
> cache.
>
> [...]
Applied, thanks!
[1/4] leds: lm3601x: Convert to use maple tree register cache
commit: c2b7575239f5d0925035f3fc3bb155d176abee80
[2/4] leds: aw200xx: Convert to use maple tree register cache
commit: 2aedfe62b4151b0abe35bf022edf18f84817afcd
[3/4] leds: lm392x: Convert to use maple tree register cache
commit: c2ecac98222a23ad8209a71ad5c1e32a8be46392
[4/4] leds: lp3952: Convert to use maple tree register cache
commit: 2997d69d888d6ee7114a89d066889a016448422a
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2023-10-05 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 15:23 Mark Brown
2023-09-29 15:23 ` [PATCH 1/4] leds: lm3601x: " Mark Brown
2023-09-29 15:23 ` [PATCH 2/4] leds: aw200xx: " Mark Brown
2023-09-29 15:23 ` [PATCH 3/4] leds: lm392x: " Mark Brown
2023-09-29 15:23 ` [PATCH 4/4] leds: lp3952: " Mark Brown
2023-10-05 11:10 ` Lee Jones [this message]
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=169650424265.688682.2460798715972634009.b4-ty@kernel.org \
--to=lee@kernel.org \
--cc=broonie@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=pavel@ucw.cz \
--cc=sboyd@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
all inboxes | Powered by JetHome®