From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Lothar Waßmann" <LW@KARO-electronics.de>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] ASoC: Fix an obvious copy paste error in an error message
Date: Sun, 11 Dec 2011 11:00:12 +0800 [thread overview]
Message-ID: <20111211030011.GF2800@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1323436589-28168-1-git-send-email-LW@KARO-electronics.de>
On Fri, Dec 09, 2011 at 02:16:29PM +0100, Lothar Waßmann wrote:
> The message was obviously copied from soc_init_codec_debugfs()
Applied, thanks.
prev parent reply other threads:[~2011-12-11 3:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 13:16 [PATCH] ASoC: Fix an obvious copy paste error in an error message Lothar Waßmann
2011-12-11 3:00 ` 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=20111211030011.GF2800@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=LW@KARO-electronics.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.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).