From: kbuild test robot <lkp@intel.com>
To: Shawn Landden <shawn@git.icu>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
"Gustavo A . R . Silva" <gustavo@embeddedor.com>,
Joe Perches <joe@perches.com>, Andy Whitcroft <apw@canonical.com>,
Shawn Landden <shawn@git.icu>
Subject: Re: [PATCH] Use fall-through attribute rather than magic comments
Date: Tue, 19 Mar 2019 18:34:34 +0800 [thread overview]
Message-ID: <201903191849.kFLSqS7A%lkp@intel.com> (raw)
In-Reply-To: <20190316033841.7659-1-shawn@git.icu>
Hi Shawn,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v5.1-rc1]
[cannot apply to next-20190319]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Shawn-Landden/Use-fall-through-attribute-rather-than-magic-comments/20190318-194548
coccinelle warnings: (new ones prefixed by >>)
>> drivers/media/dvb-frontends/drx39xyj/drxj.c:11123:48-49: Unneeded semicolon
drivers/media/dvb-frontends/drx39xyj/drxj.c:11124:48-49: Unneeded semicolon
drivers/media/dvb-frontends/drx39xyj/drxj.c:11125:47-48: Unneeded semicolon
drivers/media/dvb-frontends/drx39xyj/drxj.c:11126:47-48: Unneeded semicolon
drivers/media/dvb-frontends/drx39xyj/drxj.c:11127:48-49: Unneeded semicolon
drivers/media/dvb-frontends/drx39xyj/drxj.c:11128:40-41: Unneeded semicolon
drivers/media/dvb-frontends/drx39xyj/drxj.c:11139:40-41: Unneeded semicolon
drivers/media/dvb-frontends/drx39xyj/drxj.c:11276:39-40: Unneeded semicolon
drivers/media/dvb-frontends/drx39xyj/drxj.c:11278:40-41: Unneeded semicolon
drivers/media/dvb-frontends/drx39xyj/drxj.c:11279:40-41: Unneeded semicolon
drivers/media/dvb-frontends/drx39xyj/drxj.c:11313:40-41: Unneeded semicolon
drivers/media/dvb-frontends/drx39xyj/drxj.c:11314:40-41: Unneeded semicolon
drivers/media/dvb-frontends/drx39xyj/drxj.c:11232:40-41: Unneeded semicolon
drivers/media/dvb-frontends/drx39xyj/drxj.c:11233:40-41: Unneeded semicolon
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2019-03-19 10:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-16 3:38 Shawn Landden
2019-03-16 8:08 ` Joe Perches
2019-03-16 21:42 ` Gustavo A. R. Silva
2019-03-18 12:22 ` kbuild test robot
2019-03-18 12:30 ` kbuild test robot
2019-03-19 10:34 ` kbuild test robot [this message]
2019-03-19 10:34 ` [PATCH] fix semicolon.cocci warnings kbuild test robot
2019-06-17 15:56 ` [PATCH] Use fall-through attribute rather than magic comments Pavel Machek
2019-06-17 16:25 ` Joe Perches
2019-06-17 16:41 ` David Laight
2019-06-18 7:34 ` Pavel Machek
2019-06-18 9:30 ` Joe Perches
2019-06-18 10:45 ` Pavel Machek
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=201903191849.kFLSqS7A%lkp@intel.com \
--to=lkp@intel.com \
--cc=apw@canonical.com \
--cc=gustavo@embeddedor.com \
--cc=joe@perches.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shawn@git.icu \
/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
all inboxes | Powered by JetHome®