From: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
linux-leds@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
j.anaszewski@samsung.com
Cc: stewart@linux.vnet.ibm.com, j.anaszewski81@gmail.com,
arnd@arndb.de, cooloney@gmail.com, rpurdie@rpsys.net,
khandual@linux.vnet.ibm.com
Subject: Re: [v8,3/3] leds/powernv: Add driver for PowerNV platform
Date: Wed, 19 Aug 2015 14:12:27 +0530 [thread overview]
Message-ID: <55D44173.9020700@linux.vnet.ibm.com> (raw)
In-Reply-To: <20150818102136.0C9DD1402B5@ozlabs.org>
On 08/18/2015 03:51 PM, Michael Ellerman wrote:
> On Sat, 2015-25-07 at 05:21:10 UTC, Vasant Hegde wrote:
>> This patch implements LED driver for PowerNV platform using the existing
>> generic LED class framework.
>>
>> PowerNV platform has below type of LEDs:
>> - System attention
>> Indicates there is a problem with the system that needs attention.
>> - Identify
>> Helps the user locate/identify a particular FRU or resource in the
>> system.
>> - Fault
>> Indicates there is a problem with the FRU or resource at the
>> location with which the indicator is associated.
>
> Hi Vasant,
>
> I'm waiting for a respin of this based on the discussion between you and
> Jackek.
>
> If I don't see it soon it will miss v4.3.
Michael,
I'll post v9 in a day or two.
-Vasant
prev parent reply other threads:[~2015-08-19 8:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-25 5:21 [PATCH v8 0/3] LED driver for PowerNV platform Vasant Hegde
2015-07-25 5:21 ` [PATCH v8 1/3] powerpc/powernv: Add OPAL interfaces for accessing and modifying system LED states Vasant Hegde
2015-07-25 5:21 ` [PATCH v8 2/3] powerpc/powernv: Create LED platform device Vasant Hegde
2015-07-25 5:21 ` [PATCH v8 3/3] leds/powernv: Add driver for PowerNV platform Vasant Hegde
2015-07-26 21:41 ` Jacek Anaszewski
2015-07-27 3:41 ` Vasant Hegde
2015-07-27 9:50 ` Jacek Anaszewski
2015-07-28 13:40 ` Vasant Hegde
2015-07-28 17:40 ` Jacek Anaszewski
2015-08-19 11:54 ` Jacek Anaszewski
2015-08-19 12:06 ` Vasant Hegde
2015-07-28 6:38 ` Jacek Anaszewski
2015-07-28 10:14 ` Benjamin Herrenschmidt
2015-07-28 11:23 ` Jacek Anaszewski
2015-08-18 10:21 ` [v8,3/3] " Michael Ellerman
2015-08-19 8:42 ` Vasant Hegde [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=55D44173.9020700@linux.vnet.ibm.com \
--to=hegdevasant@linux.vnet.ibm.com \
--cc=arnd@arndb.de \
--cc=cooloney@gmail.com \
--cc=j.anaszewski81@gmail.com \
--cc=j.anaszewski@samsung.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).