From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: sound/trivial: some little typo and little fix
Date: Thu, 26 May 2011 22:07:39 +0800 [thread overview]
Message-ID: <20110526140737.GB15094@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1306410252-31534-1-git-send-email-nicolas.ferre@atmel.com>
On Thu, May 26, 2011 at 01:44:09PM +0200, Nicolas Ferre wrote:
> Hi,
>
> This is a tiny patch series with two typos and one error path fix.
> More interesting stuff will come ;-)
Applied all, thanks.
Please do try to use subject lines for your patches which are consistent
with the rest of the subsystem - it makes them much easier to apply.
prev parent reply other threads:[~2011-05-26 14:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 11:44 sound/trivial: some little typo and little fix Nicolas Ferre
2011-05-26 11:44 ` [PATCH 1/3] sound/atmel-pcm: trivial: typo in debug comment Nicolas Ferre
2011-05-26 11:05 ` Liam Girdwood
2011-05-26 11:44 ` [PATCH 2/3] sound/atmel-pcm: trivial: typo in atmel_pcm_dma_params strucutre comment Nicolas Ferre
2011-05-26 11:44 ` [PATCH 3/3] sound: atmel_ssc_dai: fix ssc error path Nicolas Ferre
2011-05-26 14:07 ` 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=20110526140737.GB15094@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).