From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: yoshii <takashi.yoshii.zj@renesas.com>,
Linux-ALSA <alsa-devel@alsa-project.org>,
Simon <horms@verge.net.au>, Magnus <magnus.damm@gmail.com>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 0/9] ASoC: sh: fsi: tidyup and cleanup FSI
Date: Tue, 24 May 2011 18:43:08 +0800 [thread overview]
Message-ID: <20110524104307.GA5953@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <w3pipt17i99.wl%kuninori.morimoto.gx@renesas.com>
On Mon, May 23, 2011 at 08:45:26PM +0900, Kuninori Morimoto wrote:
>
> Dear Mark, Liam
>
> Cc Simon, yoshii-san, Magnus
>
> These are tidyup and cleanup patches for FSI
>
> Kuninori Morimoto (9):
Applied all, thanks.
prev parent reply other threads:[~2011-05-24 10:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 11:45 [PATCH 0/9] ASoC: sh: fsi: tidyup and cleanup FSI Kuninori Morimoto
2011-05-23 11:45 ` [PATCH 1/9] ASoC: sh: fsi: tidyup parameter of fsi_stream_push Kuninori Morimoto
2011-05-23 11:46 ` [PATCH 2/9] ASoC: sh: fsi: tidyup unclear variable naming Kuninori Morimoto
2011-05-23 11:46 ` [PATCH 3/9] ASoC: sh: fsi: remove pm_runtime from fsi_dai_set_fmt Kuninori Morimoto
2011-05-23 11:46 ` [PATCH 4/9] ASoC: sh: fsi: make sure fsi_stream_push/pop access by spin lock Kuninori Morimoto
2011-05-24 10:39 ` Mark Brown
2011-05-25 0:32 ` Kuninori Morimoto
2011-05-23 11:46 ` [PATCH 5/9] ASoC: sh: fsi: add fsi_set_master_clk Kuninori Morimoto
2011-05-23 11:46 ` [PATCH 6/9] ASoC: sh: fsi: irq control moves to fsi_port_start/stop Kuninori Morimoto
2011-05-23 11:46 ` [PATCH 7/9] ASoC: sh: fsi: add fsi_hw_startup/shutdown Kuninori Morimoto
2011-05-23 11:46 ` [PATCH 8/9] ASoC: sh: fsi: remove fsi_module_init/kill Kuninori Morimoto
2011-05-23 11:46 ` [PATCH 9/9] ASoC: sh: fsi: cleanup suspend/resume Kuninori Morimoto
2011-05-23 14:43 ` [PATCH 0/9] ASoC: sh: fsi: tidyup and cleanup FSI Liam Girdwood
2011-05-24 10:43 ` Mark Brown [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=20110524104307.GA5953@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lrg@slimlogic.co.uk \
--cc=magnus.damm@gmail.com \
--cc=takashi.yoshii.zj@renesas.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.