From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ASoC: davinci-mcasp: add missing semicolon
Date: Sun, 8 Mar 2015 22:21:43 +0000 [thread overview]
Message-ID: <20150308222143.GD28806@sirena.org.uk> (raw)
In-Reply-To: <10196569.gafhWQrdaI@wuerfel>
On Sun, Mar 08, 2015 at 10:10:14PM +0100, Arnd Bergmann wrote:
> A recent patch introduced a build error because of a trivial typo, this
> gets it back to compile.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> Fixes: 6afda7f50754 ("ASoC: davinci-mcasp: Allow complete shutdown of McASP when not in use")
The same fix was sent several days ago, please submit against current
code.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150308/e0fa66dd/attachment.sig>
prev parent reply other threads:[~2015-03-08 22:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-08 21:10 [PATCH] ASoC: davinci-mcasp: add missing semicolon Arnd Bergmann
2015-03-08 22:21 ` 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=20150308222143.GD28806@sirena.org.uk \
--to=broonie@kernel.org \
--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).