From: Lee Jones <lee@kernel.org>
To: "Yuxi (Yuxi) Wang" <Yuxi.Wang@monolithicpower.com>
Cc: "pavel@ucw.cz" <pavel@ucw.cz>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"wyx137120466@gmail.com" <wyx137120466@gmail.com>
Subject: Re: [PATCH 0/2] leds: Add a driver for mp3326
Date: Tue, 31 Oct 2023 07:42:01 +0000 [thread overview]
Message-ID: <20231031074201.GP8909@google.com> (raw)
In-Reply-To: <b2a603bac3aa47e2bfbcbcd7154a4166@monolithicpower.com>
On Tue, 31 Oct 2023, Yuxi (Yuxi) Wang wrote:
> Add the binding description and the corresponding driver for
> the mps mp3326.
>
> Signed-off-by: Yuxi Wang <Yuxi.Wang@monolithicpower.com>
> Yuxi Wang (2):
> dt-bindings: leds: add mps mp3326 LED
> leds: add mp3326 driver
These 2 patches and this cover letter were all sent as individual
emails. Please re-submit the set using `git send-mail`s --thread option.
> .../devicetree/bindings/leds/leds-mp3326.yaml | 184 +++++
> drivers/leds/Kconfig | 7 +
> drivers/leds/Makefile | 1 +
> drivers/leds/leds-mp3326.c | 632 ++++++++++++++++++
> 4 files changed, 824 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/leds/leds-mp3326.yaml
> create mode 100644 drivers/leds/leds-mp3326.c
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2023-10-31 7:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 6:58 [PATCH 0/2] leds: Add a driver for mp3326 Yuxi (Yuxi) Wang
2023-10-31 7:42 ` Lee Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-24 9:30 [PATCH 0/2] leds: Add a driver for MP3326 Yuxi Wang
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=20231031074201.GP8909@google.com \
--to=lee@kernel.org \
--cc=Yuxi.Wang@monolithicpower.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=wyx137120466@gmail.com \
/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