From: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: cooloney@gmail.com, rpurdie@rpsys.net,
linuxppc-dev@lists.ozlabs.org, linux-leds@vger.kernel.org,
khandual@linux.vnet.ibm.com
Subject: Re: [PATCH 1/2] powerpc/powernv: Add OPAL interfaces for accessing and modifying system LED states
Date: Fri, 20 Mar 2015 13:37:31 +0530 [thread overview]
Message-ID: <550BD543.8080605@linux.vnet.ibm.com> (raw)
In-Reply-To: <1426832625.2581.3.camel@ellerman.id.au>
On 03/20/2015 11:53 AM, Michael Ellerman wrote:
> On Sun, 2015-03-08 at 16:44 +0530, Vasant Hegde wrote:
>> From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
>>
>> This patch registers the following two new OPAL interfaces calls
>> for the platform LED subsystem. With the help of these new OPAL calls,
>> the kernel will be able to get or set the state of various individual
>> LEDs on the system at any given location code which is passed through
>> the LED specific device tree nodes.
>>
>> (1) OPAL_LEDS_GET_INDICATOR opal_leds_get_ind
>> (2) OPAL_LEDS_SET_INDICATOR opal_leds_set_ind
>>
>> Signed-off-by: Anshuman Khandual <khandual@linux.vnet.ibm.com>
>> Signed-off-by: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>
>> ---
>> arch/powerpc/include/asm/opal.h | 19 +++++++++++++------
>
> We've split opal.h in next.
>
> Can you please rebase on top of it:
>
> https://git.kernel.org/cgit/linux/kernel/git/mpe/linux.git/log/?h=next
Sure.. will rebase and send v2 soon.
-Vasant
next prev parent reply other threads:[~2015-03-20 8:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-08 11:13 [PATCH 0/2] LED interface for PowerNV platform Vasant Hegde
2015-03-08 11:14 ` [PATCH 1/2] powerpc/powernv: Add OPAL interfaces for accessing and modifying system LED states Vasant Hegde
2015-03-19 21:35 ` Stewart Smith
2015-03-20 6:23 ` Michael Ellerman
2015-03-20 8:07 ` Vasant Hegde [this message]
2015-03-08 11:14 ` [PATCH 2/2] leds/powernv: Add driver for PowerNV platform Vasant Hegde
2015-03-19 21:35 ` Stewart Smith
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=550BD543.8080605@linux.vnet.ibm.com \
--to=hegdevasant@linux.vnet.ibm.com \
--cc=cooloney@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 \
/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).