From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: �ڻ��� <sangsu4u.park@samsung.com>
Cc: alsa-devel@alsa-project.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, lrg@ti.com,
sbkim73@samsung.com, ben-linux@fluff.org, kgene.kim@samsung.com
Subject: Re: ASoC: SAMSUNG: Change Kconfig to support all EXYNOSs
Date: Mon, 27 Aug 2012 10:13:30 -0700 [thread overview]
Message-ID: <20120827171329.GO4339@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <003001cd8361$7016a110$5043e330$@samsung.com>
On Sun, Aug 26, 2012 at 05:04:37PM +0900, �ڻ��� wrote:
> All EXYNOSs use SND_SOC_SAMSUNG configuration.
> This patch change Kconfig to support all EXYNOSs like EXYNOS4 and EXYNOS5.
git can't figure out how to apply your patch due to your character set:
fatal: cannot convert from ks_c_5601-1987 to UTF-8
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: ASoC: SAMSUNG: Change Kconfig to support all EXYNOSs
Date: Mon, 27 Aug 2012 10:13:30 -0700 [thread overview]
Message-ID: <20120827171329.GO4339@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <003001cd8361$7016a110$5043e330$@samsung.com>
On Sun, Aug 26, 2012 at 05:04:37PM +0900, ????? wrote:
> All EXYNOSs use SND_SOC_SAMSUNG configuration.
> This patch change Kconfig to support all EXYNOSs like EXYNOS4 and EXYNOS5.
git can't figure out how to apply your patch due to your character set:
fatal: cannot convert from ks_c_5601-1987 to UTF-8
next prev parent reply other threads:[~2012-08-27 17:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-26 8:04 ASoC: SAMSUNG: Change Kconfig to support all EXYNOSs 박상수
2012-08-26 8:04 ` 박상수
2012-08-27 17:13 ` Mark Brown [this message]
2012-08-27 17:13 ` Mark Brown
2012-08-27 18:06 ` Kukjin Kim
2012-08-27 18:06 ` Kukjin Kim
2012-08-27 18:08 ` Mark Brown
2012-08-27 18:08 ` Mark Brown
2012-08-27 22:59 ` Kukjin Kim
2012-08-27 22:59 ` 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=20120827171329.GO4339@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=ben-linux@fluff.org \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=lrg@ti.com \
--cc=sangsu4u.park@samsung.com \
--cc=sbkim73@samsung.com \
/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.