From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH 1/2] ARM: S3C64XX: Fix the memory mapped GPIOs on Cragganmore
Date: Fri, 30 Dec 2011 02:03:24 +0000 [thread overview]
Message-ID: <20111230020323.GE9737@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <02cc01ccc696$c741e400$55c5ac00$%kim@samsung.com>
On Fri, Dec 30, 2011 at 11:00:17AM +0900, Kukjin Kim wrote:
> Yeah, it's a little bit...so I'm sorting it out with others for next time
> :)
If you leave it for long enough I'll probably get round to doing it
myself.
WARNING: multiple messages have this Message-ID (diff)
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: Fri, 30 Dec 2011 02:03:24 +0000 [thread overview]
Message-ID: <20111230020323.GE9737@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <02cc01ccc696$c741e400$55c5ac00$%kim@samsung.com>
On Fri, Dec 30, 2011 at 11:00:17AM +0900, Kukjin Kim wrote:
> Yeah, it's a little bit...so I'm sorting it out with others for next time
> :)
If you leave it for long enough I'll probably get round to doing it
myself.
next prev parent reply other threads:[~2011-12-30 2:03 UTC|newest]
Thread overview: 14+ 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 ` Mark Brown
2011-12-29 1:23 ` [PATCH 2/2] ARM: S3C64XX: Support GPIO LEDs " Mark Brown
2011-12-29 1:23 ` Mark Brown
2011-12-29 4:01 ` Kukjin Kim
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 4:00 ` Kukjin Kim
2011-12-29 10:34 ` Mark Brown
2011-12-29 10:34 ` Mark Brown
2011-12-30 2:00 ` Kukjin Kim
2011-12-30 2:00 ` Kukjin Kim
2011-12-30 2:03 ` Mark Brown [this message]
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=20111230020323.GE9737@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.