From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: Vinod Koul <vinod.koul@intel.com>,
alsa-devel@alsa-project.org,
Harsha Priya <priya.harsha@intel.com>,
linux-kernel@vger.kernel.org, Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH 2/2] ASoC: Staticise sst_platform_dai
Date: Tue, 27 Sep 2011 11:22:00 +0100 [thread overview]
Message-ID: <20110927102159.GD2910@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1317091130.315.2.camel@phoenix>
On Tue, Sep 27, 2011 at 10:38:50AM +0800, Axel Lin wrote:
> It is not used outside this driver so no need to make the symbol global.
>
Applied, thanks.
next prev parent reply other threads:[~2011-09-27 10:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 2:38 [PATCH 1/2] ASoC: Remove unused fields in struct mfld_mc_private Axel Lin
2011-09-27 2:38 ` [PATCH 2/2] ASoC: Staticise sst_platform_dai Axel Lin
2011-09-27 10:22 ` Mark Brown [this message]
2011-09-27 10:21 ` [PATCH 1/2] ASoC: Remove unused fields in struct mfld_mc_private 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=20110927102159.GD2910@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=axel.lin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=priya.harsha@intel.com \
--cc=vinod.koul@intel.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;
as well as URLs for NNTP newsgroup(s).