linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sean MacLennan <smaclennan@pikatech.com>
To: "Grant Likely" <grant.likely@secretlab.ca>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	rpurdie@rpsys.net,
	Sean MacLennan <sean.maclennan@ottawa.kanatek.ca>,
	linuxppc-dev@ozlabs.org
Subject: Re: [RESEND][PATCH][POWERPC] PIKA Warp: Update platform code to supportRev B boards
Date: Mon, 28 Apr 2008 13:59:05 -0400	[thread overview]
Message-ID: <20080428135905.4c037b4b@lappy.seanm.ca> (raw)
In-Reply-To: <fa686aa40804281044p5fa0ef9s15107cc38fafc9fa@mail.gmail.com>

On Mon, 28 Apr 2008 11:44:19 -0600
"Grant Likely" <grant.likely@secretlab.ca> wrote:

> This looks appropriate.  You'll need to make sure that the values in
> the linux,name property meet the Linux LED naming guidelines.  I think
> this is covered in Documentation/leds-class.c.  You can also as
> Richard Purdie; the LED subsystem maintainer.

The leds name is "devicename:colour:function" where you are allowed to
leave sections blank. So I only filled in the colour ;)

I also notice that it is colour, not color.

I am hoping that this code is only for 2.6.26 and that we will switch
to the gpio-leds driver for 2.6.27. I don't want to keep supporting yet
another driver outside of the mainline kernel. Let's face it, I'm
lazy :D

Cheers,
   Sean

  reply	other threads:[~2008-04-28 17:59 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-17 19:22 [RESEND][PATCH][POWERPC] PIKA Warp: Update platform code to support Rev B boards Sean MacLennan
2008-04-27 19:25 ` [RESEND][PATCH][POWERPC] PIKA Warp: Update platform code to supportRev " Sean MacLennan
2008-04-28  0:58   ` Stephen Rothwell
2008-04-28  1:51     ` Grant Likely
2008-04-28  2:25       ` Sean MacLennan
2008-04-28  4:47         ` Grant Likely
2008-04-28 17:10           ` Sean MacLennan
2008-04-28 17:44             ` Grant Likely
2008-04-28 17:59               ` Sean MacLennan [this message]
2008-04-28 20:44                 ` Richard Purdie
2008-04-28 21:24                   ` [RESEND][PATCH][POWERPC] PIKA Warp: Update platform code tosupportRev " Sean MacLennan
2008-04-28 21:36                     ` Richard Purdie
2008-04-28  2:31     ` [RESEND][PATCH][POWERPC] PIKA Warp: Update platform code to supportRev " Sean MacLennan
2008-04-28 18:53 ` Sean MacLennan
2008-04-28 19:56   ` Grant Likely
2008-04-28 21:37     ` Sean MacLennan
2008-04-28 21:54       ` Scott Wood
2008-04-28 22:07         ` Sean MacLennan
2008-04-30  0:48           ` Josh Boyer
2008-04-28 22:07       ` Grant Likely
2008-04-29  1:47 ` [RESEND][PATCH 1/2][POWERPC] " Sean MacLennan
2008-04-29  1:50   ` [RESEND][PATCH 2/2][POWERPC] " Sean MacLennan
2008-04-29  1:58     ` Grant Likely
2008-04-29  3:27       ` Sean MacLennan
2008-04-29  3:28   ` [RESEND][PATCH 1/2][POWERPC] " Sean MacLennan
2008-04-29  5:08     ` Paul Mackerras
2008-04-29  5:42       ` [RESEND][PATCH 1/2][POWERPC] PIKA Warp: Update platform code tosupportRev " Sean MacLennan
2008-05-06 15:27     ` Sean MacLennan

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=20080428135905.4c037b4b@lappy.seanm.ca \
    --to=smaclennan@pikatech.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=rpurdie@rpsys.net \
    --cc=sean.maclennan@ottawa.kanatek.ca \
    --cc=sfr@canb.auug.org.au \
    /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).