From: Michael Ellerman <mpe@ellerman.id.au>
To: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, Stephen Rothwell <sfr@canb.auug.org.au>,
khandual@linux.vnet.ibm.com, stewart@linux.vnet.ibm.com
Subject: Re: [PATCH] powerpc/powernv: Fix mis-merge of OPAL support for LEDS driver
Date: Sat, 22 Aug 2015 21:13:35 +1000 [thread overview]
Message-ID: <1440242015.28532.1.camel@ellerman.id.au> (raw)
In-Reply-To: <55D7F547.2090607@linux.vnet.ibm.com>
On Sat, 2015-08-22 at 09:36 +0530, Vasant Hegde wrote:
> On 08/22/2015 05:12 AM, Michael Ellerman wrote:
> > When I merged the OPAL support for the powernv LEDS driver I missed a
> > hunk.
> >
> > This is slightly modified from the original patch, as the original added
> > code to opal-api.h which is not in the skiboot version, which is
> > discouraged.
>
> Yeah. I should have made sure opal-api.h is in sync with skiboot. On skiboot
> side I added below macros to fsp-leds.h instead of opal-api.h :-(
Yeah, I should have remembered too. We'll try to remember in future.
> Anyway for now these macros are used by led driver only (on both side).. Hence I
> think its fine to add to driver code itself. But we should make sure these
> strings won't change as we use them while creating sysfs entries and use that
> information to identify the type of LED.
Sure. If you want to add a comment or something saying they must not change
that's fine by me.
> > Instead those values are moved into the driver, which is the only place
> > they are used.
> >
> > Fixes: 8a8d91817aec ("powerpc/powernv: Add OPAL interfaces for accessing and modifying system LED states")
> > Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
>
> Patch looks good.
>
> Reviewed-by: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>
Thanks.
I've pushed it to next.
cheers
prev parent reply other threads:[~2015-08-22 11:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 23:42 [PATCH] powerpc/powernv: Fix mis-merge of OPAL support for LEDS driver Michael Ellerman
2015-08-22 4:06 ` Vasant Hegde
2015-08-22 11:13 ` Michael Ellerman [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=1440242015.28532.1.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=hegdevasant@linux.vnet.ibm.com \
--cc=khandual@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=sfr@canb.auug.org.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.