From: Sangsu Park <sangsu4u.park@samsung.com>
To: 'Mark Brown' <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, linux-samsung-soc@vger.kernel.org,
sbkim73@samsung.com, 'Kukjin Kim' <kgene.kim@samsung.com>,
ben-linux@fluff.org, lrg@ti.com,
linux-arm-kernel@lists.infradead.org
Subject: RE: [PATCH] ASoC: SAMSUNG: Add SND_SOC_DAIFMT_CONT option for snd_soc_set_fmt()
Date: Thu, 06 Sep 2012 17:57:45 +0900 [thread overview]
Message-ID: <006601cd8c0d$aeca9d30$0c5fd790$@samsung.com> (raw)
In-Reply-To: <20120906002145.GU10580@opensource.wolfsonmicro.com>
On Thurs, Sep 06, 2012 at 9:22 AM +0900, Mark Brown wrote:
> On Mon, Sep 03, 2012 at 11:10:03AM +0900, Sangsu Park wrote:
> > On Sun, Aug 31, 2012 at 2:43 AM +0900, Mark Brown wrote:
> > > On Wed, Aug 29, 2012 at 08:06:32PM +0900, Sangsu Park wrote:
>
> > > Please check your mailer configuration, it looks like it's reformatting
> > > all the text with much longer line widths.
>
> > I've changed line width configuration. Is it ok now?
>
> Looks like it, thanks.
>
> > Do you think that changing pcm driver is right approach?
> > Then I'll fix pcm driver. (I think that pcm driver has some strange code.)
>
> Well, we could do both. It'd certainly be more natural to make it have
> a default given that this isn't something that normally needs to be
> configured.
>
Then, I'll fix pcm driver to use default given
and resend that patch.
Thanks.
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2012-09-06 8:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-26 8:45 [PATCH] ASoC: SAMSUNG: Add SND_SOC_DAIFMT_CONT option for snd_soc_set_fmt() 박상수
2012-08-27 20:45 ` Mark Brown
2012-08-29 11:06 ` Sangsu Park
2012-08-30 17:43 ` Mark Brown
2012-09-03 2:10 ` Sangsu Park
2012-09-06 0:21 ` Mark Brown
2012-09-06 8:57 ` Sangsu Park [this message]
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='006601cd8c0d$aeca9d30$0c5fd790$@samsung.com' \
--to=sangsu4u.park@samsung.com \
--cc=alsa-devel@alsa-project.org \
--cc=ben-linux@fluff.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=lrg@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox