linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Correct bad gpio naming
Date: Sun, 22 Jan 2012 12:31:24 -0700	[thread overview]
Message-ID: <20120122193124.GX4223@ponder.secretlab.ca> (raw)
In-Reply-To: <4F1C4E25.6070801@antcom.de>

On Sun, Jan 22, 2012 at 06:57:57PM +0100, Roland Stigge wrote:
> One of the GPIO names in drivers/gpio/gpio-lpc32xx.c
> was bad. Renaming gpi000 -> gpio00
> 
> Signed-off-by: Roland Stigge <stigge@antcom.de>

Applied.  Careful though, this patch was corrupt (missing carriage
return before 'static' and had to be applied by hand.

g.

> 
> diff --git a/drivers/gpio/gpio-lpc32xx.c b/drivers/gpio/gpio-lpc32xx.c
> index 5b69480..ddfacc5 100644
> --- a/drivers/gpio/gpio-lpc32xx.c
> +++ b/drivers/gpio/gpio-lpc32xx.c
> @@ -96,7 +96,7 @@ static const char *gpio_p2_names[LPC32XX_GPIO_P2_MAX] = {
>  };
>   static const char *gpio_p3_names[LPC32XX_GPIO_P3_MAX] = {
> -	"gpi000", "gpio01", "gpio02", "gpio03",
> +	"gpio00", "gpio01", "gpio02", "gpio03",
>  	"gpio04", "gpio05"
>  };
> 

  reply	other threads:[~2012-01-22 19:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-22 17:57 [PATCH] Correct bad gpio naming Roland Stigge
2012-01-22 19:31 ` Grant Likely [this message]
2012-01-24 15:59 ` Wolfram Sang
2012-01-24 16:32   ` Roland Stigge
2012-01-24 19:25     ` LPC32xx status (Re: [PATCH] Correct bad gpio naming) Wolfram Sang
2012-01-24 20:38       ` Roland Stigge
2012-01-24 21:09         ` Wolfram Sang
  -- strict thread matches above, loose matches on Subject: below --
2012-01-10 13:36 [PATCH] Correct bad gpio naming stigge at antcom.de

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=20120122193124.GX4223@ponder.secretlab.ca \
    --to=grant.likely@secretlab.ca \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).