All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@lists.ozlabs.org
Cc: j.anaszewski@samsung.com, linux-leds@vger.kernel.org,
	Stewart Smith <stewart@linux.vnet.ibm.com>
Subject: Re: [v2] powerpc/configs: Enable LEDS support
Date: Thu, 27 Aug 2015 17:12:29 +0530	[thread overview]
Message-ID: <55DEF7A5.6070407@linux.vnet.ibm.com> (raw)
In-Reply-To: <20150827102619.BEB9214018C@ozlabs.org>

On 08/27/2015 03:56 PM, Michael Ellerman wrote:
> On Thu, 2015-27-08 at 06:04:10 UTC, Vasant Hegde wrote:
>> Commit 84ad6e5c added LEDS support for PowerNV platform. Lets
>> update ppc64_defconfig to pick LEDS driver.
>>
>> PowerNV LEDS driver looks for "/ibm,opal/leds" node in device
>> tree and loads if this node exists. Hence added it as 'm'.
>>
>> Also note that powernv LEDS driver needs NEW_LEDS and LEDS_CLASS
>> as well. Hence added them to config file.
>>
>> Suggested-by: Michael Ellerman <mpe@ellerman.id.au>
>> Signed-off-by: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>
>> Cc: Stewart Smith <stewart@linux.vnet.ibm.com>
>> ---
>> Changes in v2:
>>   - As suggested by Stewart updated patch description
>>
>> Michael,
>>   This is PowerNV specific config. Hence I've not updated pseries_defconfig.
>>   Let me know if you want me to update pseries_defconfig config as well.
> 
> I've added it to pseries_defconfig also, no need to resend.

Thanks!

-Vasant

  reply	other threads:[~2015-08-27 11:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-27  6:04 [PATCH v2] powerpc/configs: Enable LEDS support Vasant Hegde
2015-08-27 10:26 ` [v2] " Michael Ellerman
2015-08-27 10:26   ` Michael Ellerman
2015-08-27 11:42   ` Vasant Hegde [this message]
2015-08-27 21:58 ` Michael Ellerman
2015-08-27 21:58   ` Michael Ellerman

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=55DEF7A5.6070407@linux.vnet.ibm.com \
    --to=hegdevasant@linux.vnet.ibm.com \
    --cc=j.anaszewski@samsung.com \
    --cc=linux-leds@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.