From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: S3C64XX: Update configuration for WM5102 module on Cragganmore
Date: Fri, 10 Aug 2012 11:07:13 +0100 [thread overview]
Message-ID: <20120810100713.GH24328@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <0db901cd76b4$7daf1730$790d4590$%kim@samsung.com>
On Fri, Aug 10, 2012 at 01:56:23PM +0900, Kukjin Kim wrote:
> Probably, this patch needs following?
> If you're ok, I will fix build error by above when I apply.
Yes, thanks.
next prev parent reply other threads:[~2012-08-10 10:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 18:05 [PATCH 1/2] ARM: S3C64XX: Update configuration for WM5102 module on Cragganmore Mark Brown
2012-08-09 18:05 ` [PATCH 2/2] ARM: S3C64XX: Register audio platform devices for Bells " Mark Brown
2012-08-10 4:56 ` [PATCH 1/2] ARM: S3C64XX: Update configuration for WM5102 module " Kukjin Kim
2012-08-10 10:07 ` Mark Brown [this message]
2012-08-11 5:08 ` Kukjin Kim
2012-08-13 12:24 ` Mark Brown
2012-08-23 9:45 ` Kukjin Kim
2012-08-23 15:20 ` Mark Brown
2012-08-28 23:30 ` 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=20120810100713.GH24328@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).