From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: S3C64XX: Fix the memory mapped GPIOs on Cragganmore
Date: Thu, 29 Dec 2011 10:34:12 +0000 [thread overview]
Message-ID: <20111229103412.GC2909@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <029301ccc5de$58557970$09006c50$%kim@samsung.com>
On Thu, Dec 29, 2011 at 01:00:04PM +0900, Kukjin Kim wrote:
> And Mark, how about using DEFINE_RES_XXX() like following?
That's fine, though the mmgpio one does need to have the name added.
next prev parent reply other threads:[~2011-12-29 10:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 1:23 [PATCH 1/2] ARM: S3C64XX: Fix the memory mapped GPIOs on Cragganmore Mark Brown
2011-12-29 1:23 ` [PATCH 2/2] ARM: S3C64XX: Support GPIO LEDs " Mark Brown
2011-12-29 4:01 ` Kukjin Kim
2011-12-29 4:00 ` [PATCH 1/2] ARM: S3C64XX: Fix the memory mapped GPIOs " Kukjin Kim
2011-12-29 10:34 ` Mark Brown [this message]
2011-12-30 2:00 ` Kukjin Kim
2011-12-30 2:03 ` Mark Brown
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=20111229103412.GC2909@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--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).