From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: Vinod Koul <vinod.koul@linux.intel.com>,
Harsha Priya <priya.harsha@intel.com>,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] ASoC: sn95031: Do not use static variable for channel_index
Date: Fri, 30 Sep 2011 12:51:03 +0100 [thread overview]
Message-ID: <20110930115103.GE5366@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1317362219.6646.2.camel@phoenix>
On Fri, Sep 30, 2011 at 01:56:59PM +0800, Axel Lin wrote:
> No reason to use static variable for channel_index.
Applied, thanks.
prev parent reply other threads:[~2011-09-30 11:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 5:56 [PATCH] ASoC: sn95031: Do not use static variable for channel_index Axel Lin
2011-09-30 11:51 ` 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=20110930115103.GE5366@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@linux.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).