mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang@pengutronix.de>
To: Roland Stigge <stigge@antcom.de>
Cc: linux@arm.linux.org.uk, linux-arm-kernel@lists.infradead.org,
	grant.likely@secretlab.ca, linus.walleij@stericsson.com,
	linux-kernel@vger.kernel.org, Kevin Wells <kevin.wells@nxp.com>
Subject: Re: [PATCH] Correct bad gpio naming
Date: Tue, 24 Jan 2012 16:59:21 +0100	[thread overview]
Message-ID: <20120124155921.GH2609@pengutronix.de> (raw)
In-Reply-To: <4F1C4E25.6070801@antcom.de>

[-- Attachment #1: Type: text/plain, Size: 750 bytes --]

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>

Since you are modifying LPC32xx :) Which kernel version do you run? I
was trying to get a board up with 3.0 (not booting) and 3.3-rc1 (build
breakage). I even thought about removing that mach, since vital parts
seem to be missing (Net, NAND) or broken. So, I am interested if there
are still users.

CCing Kevin Wells, too: Any plans from NXP?

Thanks,

   Wolfram

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2012-01-24 15:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-22 17:57 Roland Stigge
2012-01-22 19:31 ` Grant Likely
2012-01-24 15:59 ` Wolfram Sang [this message]
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

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=20120124155921.GH2609@pengutronix.de \
    --to=w.sang@pengutronix.de \
    --cc=grant.likely@secretlab.ca \
    --cc=kevin.wells@nxp.com \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=stigge@antcom.de \
    /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
all inboxes | Powered by JetHome®