From: Simon Horman <horms@verge.net.au>
To: Mark Brown <broonie@kernel.org>
Cc: Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>,
Morimoto <kuninori.morimoto.gx@renesas.com>,
Linux-SH <linux-sh@vger.kernel.org>,
Linux-ALSA <alsa-devel@alsa-project.org>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH 0/2][RFC] ASoC: fsi/rcar: fixup SND_SOC_DAIFMT_CBx_CFx flags
Date: Mon, 17 Mar 2014 09:15:43 +0900 [thread overview]
Message-ID: <20140317001543.GC31012@verge.net.au> (raw)
In-Reply-To: <20140314102614.GT366@sirena.org.uk>
On Fri, Mar 14, 2014 at 10:26:14AM +0000, Mark Brown wrote:
> On Fri, Mar 14, 2014 at 08:55:51AM +0900, Simon Horman wrote:
>
> > Do you anticipate that they will end up in v3.15-rcX?
> > If not, could I get a branch with stable commit ids that
> > I can use as a basis for futher shmobile changes: I'd
> > like avoid conflicts bubbling up.
>
> Yes, the idea is to get this to Linus as fast as possible.
Great, that is ideal from my POV.
next prev parent reply other threads:[~2014-03-17 0:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 6:47 [PATCH 0/2][RFC] ASoC: fsi/rcar: fixup SND_SOC_DAIFMT_CBx_CFx flags Kuninori Morimoto
2014-03-12 6:48 ` [PATCH 1/2][RFC] ASoC: fsi: " Kuninori Morimoto
2014-03-13 23:55 ` Simon Horman
2014-03-12 6:48 ` [PATCH 2/2][RFC] ASoC: rcar: " Kuninori Morimoto
2014-03-13 10:48 ` [PATCH 0/2][RFC] ASoC: fsi/rcar: " Mark Brown
2014-03-13 23:55 ` Kuninori Morimoto
2014-03-13 23:55 ` Simon Horman
2014-03-14 10:26 ` Mark Brown
2014-03-17 0:15 ` Simon Horman [this message]
2014-03-14 0:54 ` [PATCH 0/2 v2] " Kuninori Morimoto
2014-03-14 0:56 ` [PATCH 1/2 v2] ASoC: fsi: " Kuninori Morimoto
2014-03-14 19:31 ` Mark Brown
2014-03-14 0:56 ` [PATCH 2/2] ASoC: rcar: " Kuninori Morimoto
2014-03-14 19:34 ` 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=20140317001543.GC31012@verge.net.au \
--to=horms@verge.net.au \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kuninori.morimoto.gx@gmail.com \
--cc=kuninori.morimoto.gx@renesas.com \
--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).