From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org, Takashi Iwai <tiwai@suse.com>,
Chen-Yu Tsai <wens@csie.org>, Mark Brown <broonie@kernel.org>,
kbuild-all@01.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ASoC: sunxi: fix semicolon.cocci warnings
Date: Thu, 30 Jun 2016 20:45:52 +0200 [thread overview]
Message-ID: <20160630184552.GA5485@lukather> (raw)
In-Reply-To: <20160630142810.GA12218@lkp-nex05>
[-- Attachment #1.1: Type: text/plain, Size: 548 bytes --]
1;4205;0c
On Thu, Jun 30, 2016 at 10:28:10PM +0800, kbuild test robot wrote:
> sound/soc/sunxi/sun4i-i2s.c:624:2-3: Unneeded semicolon
>
>
> Remove unneeded semicolon.
>
> Generated by: scripts/coccinelle/misc/semicolon.cocci
>
> CC: Maxime Ripard <maxime.ripard@free-electrons.com>
> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
Acked-by: Maxime Ripard <maxime.ripard@free-electrons.com>
Thanks,
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2016-06-30 18:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 14:28 [asoc:topic/sunxi 2/2] sound/soc/sunxi/sun4i-i2s.c:624:2-3: Unneeded semicolon kbuild test robot
2016-06-30 14:28 ` [PATCH] ASoC: sunxi: fix semicolon.cocci warnings kbuild test robot
2016-06-30 18:45 ` Maxime Ripard [this message]
2016-07-01 9:54 ` Applied "ASoC: sunxi: fix semicolon.cocci warnings" to the asoc tree Mark Brown
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=20160630184552.GA5485@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.com \
--cc=wens@csie.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).