From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: linuxppc-dev@lists.ozlabs.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
mpe@ellerman.id.au
Cc: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>,
linux-leds@vger.kernel.org, stewart@linux.vnet.ibm.com,
j.anaszewski81@gmail.com, cooloney@gmail.com, rpurdie@rpsys.net,
khandual@linux.vnet.ibm.com
Subject: Re: [PATCH v4 0/3] LED interface for PowerNV platform
Date: Mon, 22 Jun 2015 10:03:37 +0200 [thread overview]
Message-ID: <5587C159.3060706@samsung.com> (raw)
In-Reply-To: <55792BB3.3000102@linux.vnet.ibm.com>
On 06/11/2015 08:33 AM, Vasant Hegde wrote:
> On 04/28/2015 03:39 PM, Vasant Hegde wrote:
>> The following series implements LED driver for PowerNV platform.
>
> Ben, Michael,
>
> Can you please review/ACK this patchset?
Yeah, we are waiting for ppc maintainer's ack, also to clarify
DT related issues. Ben himself asked to wait for the ack in the
message [1]. We are waiting for almost two months now :)
[1] http://www.spinics.net/lists/linux-leds/msg03557.html
--
Best Regards,
Jacek Anaszewski
prev parent reply other threads:[~2015-06-22 8:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 10:09 [PATCH v4 0/3] LED interface for PowerNV platform Vasant Hegde
2015-04-28 10:09 ` [PATCH v4 1/3] powerpc/powernv: Add OPAL interfaces for accessing and modifying system LED states Vasant Hegde
2015-06-25 1:04 ` Benjamin Herrenschmidt
2015-04-28 10:10 ` [PATCH v4 2/3] powerpc/powernv: Create LED platform device Vasant Hegde
2015-06-25 1:05 ` Benjamin Herrenschmidt
2015-04-28 10:10 ` [PATCH v4 3/3] leds/powernv: Add driver for PowerNV platform Vasant Hegde
2015-04-28 10:18 ` Arnd Bergmann
2015-04-30 15:04 ` Vasant Hegde
2015-04-30 14:29 ` Jacek Anaszewski
2015-04-30 15:08 ` Vasant Hegde
2015-06-25 1:09 ` Benjamin Herrenschmidt
2015-06-26 5:17 ` Vasant Hegde
2015-06-11 6:33 ` [PATCH v4 0/3] LED interface " Vasant Hegde
2015-06-22 8:03 ` Jacek Anaszewski [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=5587C159.3060706@samsung.com \
--to=j.anaszewski@samsung.com \
--cc=benh@kernel.crashing.org \
--cc=cooloney@gmail.com \
--cc=hegdevasant@linux.vnet.ibm.com \
--cc=j.anaszewski81@gmail.com \
--cc=khandual@linux.vnet.ibm.com \
--cc=linux-leds@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=rpurdie@rpsys.net \
--cc=stewart@linux.vnet.ibm.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).