From: Jarkko Nikula <jarkko.nikula@bitmer.com>
To: Michael Opdenacker <michael.opdenacker@linaro.org>
Cc: lrg@ti.com, broonie@opensource.wolfsonmicro.com, perex@perex.cz,
tiwai@suse.de, linux-omap@vger.kernel.org,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] omap: sound: fix "ambiguous else" warning
Date: Mon, 10 Oct 2011 09:54:26 +0300 [thread overview]
Message-ID: <4E9296A2.50003@bitmer.com> (raw)
In-Reply-To: <1318223228-15671-2-git-send-email-michael.opdenacker@linaro.org>
Hi
On 10/10/2011 08:07 AM, Michael Opdenacker wrote:
> This patch applies against Tony Lindgren's linux-omap tree
> It fixes "ambiguous else" warnings at compile time.
>
> Signed-off-by: Michael Opdenacker<michael.opdenacker@linaro.org>
> ---
> sound/soc/omap/omap-mcbsp.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
This is already fixed in ASoC tree by following commit
commit 141947e6ceb8f82fe8382b26f093bb379af9af15
Author: Peter Ujfalusi <peter.ujfalusi@ti.com>
Date: Mon Sep 26 10:56:42 2011 +0300
ASoC: omap-mcbsp: Fix compile time warning about ambiguous ‘else’
--
Jarkko
next prev parent reply other threads:[~2011-10-10 6:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 5:07 [PATCH 0/2] omap: sound: style and warning fixes Michael Opdenacker
2011-10-10 5:07 ` [PATCH 1/2] omap: sound: fix "ambiguous else" warning Michael Opdenacker
2011-10-10 6:54 ` Jarkko Nikula [this message]
2011-10-10 7:38 ` Michael Opdenacker
2011-10-10 5:07 ` [PATCH 2/2] omap: sound: fix checkpatch.pl error Michael Opdenacker
2011-10-10 6:56 ` Jarkko Nikula
2011-10-10 6:56 ` Jarkko Nikula
2011-10-10 9:32 ` Mark Brown
2011-10-10 13:03 ` Michael Opdenacker
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=4E9296A2.50003@bitmer.com \
--to=jarkko.nikula@bitmer.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=michael.opdenacker@linaro.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.