From: Linus Walleij <linus.walleij@linaro.org>
To: cy_huang <u0084500@gmail.com>
Cc: Pavel Machek <pavel@ucw.cz>, Dan Murphy <dmurphy@ti.com>,
Rob Herring <robh+dt@kernel.org>,
Linux LED Subsystem <linux-leds@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
cy_huang@richtek.com,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] leds: rt4505: Add support for Richtek RT4505 flash LED controller
Date: Mon, 16 Nov 2020 00:55:08 +0100 [thread overview]
Message-ID: <CACRpkdbGs-LEWie2uzZEHxrac-0tuHqRtdDP0D22KnXKQ3rqGQ@mail.gmail.com> (raw)
In-Reply-To: <1604284946-16254-1-git-send-email-u0084500@gmail.com>
On Mon, Nov 2, 2020 at 3:42 AM cy_huang <u0084500@gmail.com> wrote:
> drivers/leds/flash/Kconfig | 17 ++
> drivers/leds/flash/Makefile | 2 +
> drivers/leds/flash/leds-rt4505.c | 430 +++++++++++++++++++++++++++++++++++++++
Hm Pavel also asked me to create this directory and structure,
so if this gets applied to the MFD tree there will be some
serious clash.
I can rebase on this patch set if Lee applies it first, they you
need an immutable branch from Lee first to set up the build
infrastructure in the LEDs tree, and then I can rebase on your
tree once you have pulled in that.
Yours,
Linus Walleij
next prev parent reply other threads:[~2020-11-15 23:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 2:42 [PATCH v2 1/2] leds: rt4505: Add support for Richtek RT4505 flash LED controller cy_huang
2020-11-02 2:42 ` [PATCH v2 2/2] leds: rt4505: Add DT binding document for Richtek RT4505 cy_huang
2020-11-02 20:44 ` [PATCH v2 1/2] leds: rt4505: Add support for Richtek RT4505 flash LED controller Jacek Anaszewski
2021-03-25 7:52 ` ChiYuan Huang
2021-03-25 10:01 ` Pavel Machek
2021-03-25 10:19 ` ChiYuan Huang
2021-03-25 10:27 ` Pavel Machek
2020-11-15 23:55 ` Linus Walleij [this message]
2020-11-17 1:10 ` ChiYuan Huang
2020-11-17 17:59 ` Linus Walleij
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=CACRpkdbGs-LEWie2uzZEHxrac-0tuHqRtdDP0D22KnXKQ3rqGQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=cy_huang@richtek.com \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=u0084500@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;
as well as URLs for NNTP newsgroup(s).