From: Pavel Machek <pavel@ucw.cz>
To: ChiYuan Huang <u0084500@gmail.com>
Cc: Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Dan Murphy <dmurphy@ti.com>, Rob Herring <robh+dt@kernel.org>,
Linux LED Subsystem <linux-leds@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
cy_huang <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: Thu, 25 Mar 2021 11:01:22 +0100 [thread overview]
Message-ID: <20210325100122.GA4619@amd> (raw)
In-Reply-To: <CADiBU3-pDdoCioKc1mZwx7tp+_kfcN=4j-iMOT9LupXW03qwNA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 638 bytes --]
Hi!
> > > create mode 100644 drivers/leds/flash/Kconfig
> > > create mode 100644 drivers/leds/flash/Makefile
> > > create mode 100644 drivers/leds/flash/leds-rt4505.c
> >
> > Acked-by: Jacek Anaszewski <jacek.anaszewski@gmail.com>
> >
> Any problem with this patch? Do I need to submit it again?
It won't apply on current next.
So please: Merge ACKs, reorder it so that docs goes first, port it to
To gitolite.kernel.org:pub/scm/linux/kernel/git/pavel/linux-leds.git
34731ed13e8a..85674b0e40d9 for-next -> for-next
and resubmit.
Thanks you,
Pavel
--
http://www.livejournal.com/~pavelmachek
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2021-03-25 10:02 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 [this message]
2021-03-25 10:19 ` ChiYuan Huang
2021-03-25 10:27 ` Pavel Machek
2020-11-15 23:55 ` Linus Walleij
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=20210325100122.GA4619@amd \
--to=pavel@ucw.cz \
--cc=cy_huang@richtek.com \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--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).