From: Mark Brown <broonie@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Pavel Machek <pavel@ucw.cz>,
Lee Jones <lee@kernel.org>
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: [PATCH 0/4] leds: Convert to use maple tree register cache
Date: Fri, 29 Sep 2023 17:23:34 +0200 [thread overview]
Message-ID: <20230929-leds-maple-v1-0-ba5f9dcb1e75@kernel.org> (raw)
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.
Signed-off-by: Mark Brown <broonie@kernel.org>
---
Mark Brown (4):
leds: lm3601x: Convert to use maple tree register cache
leds: aw200xx: Convert to use maple tree register cache
leds: lm392x: Convert to use maple tree register cache
leds: lp3952: Convert to use maple tree register cache
drivers/leds/flash/leds-lm3601x.c | 2 +-
drivers/leds/leds-aw200xx.c | 2 +-
drivers/leds/leds-lm3692x.c | 2 +-
drivers/leds/leds-lp3952.c | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
---
base-commit: 6465e260f48790807eef06b583b38ca9789b6072
change-id: 20230929-leds-maple-746230bd3ab6
Best regards,
--
Mark Brown <broonie@kernel.org>
next reply other threads:[~2023-09-29 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 15:23 Mark Brown [this message]
2023-09-29 15:23 ` [PATCH 1/4] leds: lm3601x: Convert to use maple tree register cache 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 ` [PATCH 0/4] leds: " 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=20230929-leds-maple-v1-0-ba5f9dcb1e75@kernel.org \
--to=broonie@kernel.org \
--cc=lee@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;
as well as URLs for NNTP newsgroup(s).