From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: S3C64XX: Fix up IRQ mapping for balblair on Cragganmore
Date: Fri, 2 Nov 2012 14:22:39 +0000 [thread overview]
Message-ID: <20121102142238.GX4413@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1351861454-20032-1-git-send-email-dp@opensource.wolfsonmicro.com>
On Fri, Nov 02, 2012 at 01:04:14PM +0000, Dimitris Papastamos wrote:
> We are using S3C_EINT(4) instead of S3C_EINT(5).
Reviwed-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20121102/5ecfdda4/attachment.sig>
next prev parent reply other threads:[~2012-11-02 14:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 13:04 [PATCH v2] ARM: S3C64XX: Fix up IRQ mapping for balblair on Cragganmore Dimitris Papastamos
2012-11-02 14:22 ` Mark Brown [this message]
2012-11-06 10:52 ` Kukjin Kim
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=20121102142238.GX4413@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).