From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH 1/2] ASoC: Remove a unused variables from i.MX FIQ runtime data
Date: Thu, 25 Feb 2010 12:57:46 +0000 [thread overview]
Message-ID: <1267102666.4037.161.camel@odin> (raw)
In-Reply-To: <1267102330-13294-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On Thu, 2010-02-25 at 12:52 +0000, Mark Brown wrote:
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Both Acked-by: Liam Girdwood <lrg@slimlogic.co.uk>
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2010-02-25 12:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 12:52 [PATCH 1/2] ASoC: Remove a unused variables from i.MX FIQ runtime data Mark Brown
2010-02-25 12:52 ` [PATCH 2/2] ASoC: Check progress when reporting periods from i.MX FIQ handler Mark Brown
2010-02-25 12:57 ` Liam Girdwood [this message]
2010-02-25 14:59 ` [PATCH 1/2] ASoC: Remove a unused variables from i.MX FIQ runtime data Sascha Hauer
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=1267102666.4037.161.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=s.hauer@pengutronix.de \
/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).