From: Mark Brown <broonie@kernel.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>, Simon <horms@verge.net.au>,
Linux-SH <linux-sh@vger.kernel.org>,
Linux-ALSA <alsa-devel@alsa-project.org>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH 0/3] ARM: shmobile: armadillo: fixup CPU settings
Date: Thu, 26 Mar 2015 17:36:28 +0000 [thread overview]
Message-ID: <20150326173628.GX3572@sirena.org.uk> (raw)
In-Reply-To: <87fv8v4353.wl%kuninori.morimoto.gx@renesas.com>
[-- Attachment #1: Type: text/plain, Size: 269 bytes --]
On Tue, Mar 24, 2015 at 01:05:02AM +0000, Kuninori Morimoto wrote:
> So, I think keeping current FSI driver as-is is more safety for old boards.
> I tested these patches on latest Mark's branch
Simon, are these OK for me to apply or do you want to apply them?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-03-26 17:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 1:05 [PATCH 0/3] ARM: shmobile: armadillo: fixup CPU settings Kuninori Morimoto
2015-03-24 1:06 ` [PATCH 1/3] ARM: shmobile: armadillo800eva: Properly specify HDMI audio link format Kuninori Morimoto
2015-03-24 1:06 ` [PATCH 2/3] ARM: shmobile: armadillo800eva: fix clock inversion Kuninori Morimoto
2015-03-24 1:07 ` [PATCH 3/3] ASoC: simple-card: Remove support for setting differing DAI formats Kuninori Morimoto
2015-04-10 7:15 ` Kuninori Morimoto
2015-04-10 8:52 ` [alsa-devel] " Lars-Peter Clausen
2015-04-10 9:21 ` Kuninori Morimoto
2015-04-10 9:25 ` Lars-Peter Clausen
2015-03-26 17:36 ` Mark Brown [this message]
2015-03-27 0:55 ` [PATCH 0/3] ARM: shmobile: armadillo: fixup CPU settings Simon Horman
2015-03-27 1:35 ` 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=20150326173628.GX3572@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-sh@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 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).