From: Michal Simek <michal.simek@petalogix.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: monstr@monstr.eu, linux-kernel@vger.kernel.org, raph@8d.com,
dbrownell@users.sourceforge.net, diego.dompe@ridgerun.com,
rpurdie@linux.intel.com,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] leds: gpio-leds: Fix typographics fault
Date: Wed, 22 Jul 2009 08:33:27 +0200 [thread overview]
Message-ID: <4A66B2B7.7000407@petalogix.com> (raw)
In-Reply-To: <fa686aa40907020755l16d38a44t1a759d9731fb1022@mail.gmail.com>
Hi Richard and Andrew,
can you please handle this patch through your tree? Or through mm tree.
Thanks,
Michal
> On Thu, Jul 2, 2009 at 12:12 AM, <monstr@monstr.eu> wrote:
>
>> From: Michal Simek <monstr@monstr.eu>
>>
>> Signed-off-by: Michal Simek <monstr@monstr.eu>
>>
>
> Acked-by: Grant Likely <grant.likely@secretlab.ca>
>
>
>> ---
>> drivers/leds/leds-gpio.c | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/drivers/leds/leds-gpio.c b/drivers/leds/leds-gpio.c
>> index 6b06638..107e5ae 100644
>> --- a/drivers/leds/leds-gpio.c
>> +++ b/drivers/leds/leds-gpio.c
>> @@ -80,7 +80,7 @@ static int __devinit create_gpio_led(const struct gpio_led *template,
>>
>> /* skip leds that aren't available */
>> if (!gpio_is_valid(template->gpio)) {
>> - printk(KERN_INFO "Skipping unavilable LED gpio %d (%s)\n",
>> + printk(KERN_INFO "Skipping unavailable LED gpio %d (%s)\n",
>> template->gpio, template->name);
>> return 0;
>> }
>> --
>> 1.5.5.1
>>
>>
>>
>
>
>
>
--
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663
prev parent reply other threads:[~2009-07-22 6:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 6:12 [PATCH] leds: gpio-leds: Fix typographics fault monstr
2009-07-02 14:55 ` Grant Likely
2009-07-22 6:33 ` Michal Simek [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=4A66B2B7.7000407@petalogix.com \
--to=michal.simek@petalogix.com \
--cc=akpm@linux-foundation.org \
--cc=dbrownell@users.sourceforge.net \
--cc=diego.dompe@ridgerun.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=monstr@monstr.eu \
--cc=raph@8d.com \
--cc=rpurdie@linux.intel.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