From: kbuild test robot <lkp@intel.com>
To: Quytelda Kahja <quytelda@tamalin.org>
Cc: kbuild-all@01.org, gregkh@linuxfoundation.org,
devel@driverdev.osuosl.org, Quytelda Kahja <quytelda@tamalin.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: fwserial: remove unnecessary parenthesis
Date: Fri, 2 Feb 2018 10:14:20 +0800 [thread overview]
Message-ID: <201802021052.heNR0okL%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180201053951.18688-1-quytelda@tamalin.org>
[-- Attachment #1: Type: text/plain, Size: 3925 bytes --]
Hi Quytelda,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on staging/staging-testing]
[also build test WARNING on v4.15 next-20180201]
[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/Quytelda-Kahja/Staging-fwserial-remove-unnecessary-parenthesis/20180202-093148
config: i386-randconfig-x019-201804 (attached as .config)
compiler: gcc-7 (Debian 7.2.0-12) 7.2.1 20171025
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All warnings (new ones prefixed by >>):
In file included from include/linux/kernel.h:10:0,
from drivers/staging//fwserial/dma_fifo.c:8:
drivers/staging//fwserial/dma_fifo.c: In function 'dma_fifo_out_complete':
>> drivers/staging//fwserial/dma_fifo.c:253:44: warning: suggest parentheses around comparison in operand of '==' [-Wparentheses]
if (FAIL(fifo, list_empty(&fifo->pending) != fifo->open == 0,
~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~
include/linux/compiler.h:58:30: note: in definition of macro '__trace_if'
if (__builtin_constant_p(!!(cond)) ? !!(cond) : \
^~~~
>> drivers/staging//fwserial/dma_fifo.c:253:2: note: in expansion of macro 'if'
if (FAIL(fifo, list_empty(&fifo->pending) != fifo->open == 0,
^~
>> drivers/staging//fwserial/dma_fifo.c:253:6: note: in expansion of macro 'FAIL'
if (FAIL(fifo, list_empty(&fifo->pending) != fifo->open == 0,
^~~~
>> drivers/staging//fwserial/dma_fifo.c:253:44: warning: suggest parentheses around comparison in operand of '==' [-Wparentheses]
if (FAIL(fifo, list_empty(&fifo->pending) != fifo->open == 0,
~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~
include/linux/compiler.h:58:42: note: in definition of macro '__trace_if'
if (__builtin_constant_p(!!(cond)) ? !!(cond) : \
^~~~
>> drivers/staging//fwserial/dma_fifo.c:253:2: note: in expansion of macro 'if'
if (FAIL(fifo, list_empty(&fifo->pending) != fifo->open == 0,
^~
>> drivers/staging//fwserial/dma_fifo.c:253:6: note: in expansion of macro 'FAIL'
if (FAIL(fifo, list_empty(&fifo->pending) != fifo->open == 0,
^~~~
>> drivers/staging//fwserial/dma_fifo.c:253:44: warning: suggest parentheses around comparison in operand of '==' [-Wparentheses]
if (FAIL(fifo, list_empty(&fifo->pending) != fifo->open == 0,
~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~
include/linux/compiler.h:69:16: note: in definition of macro '__trace_if'
______r = !!(cond); \
^~~~
>> drivers/staging//fwserial/dma_fifo.c:253:2: note: in expansion of macro 'if'
if (FAIL(fifo, list_empty(&fifo->pending) != fifo->open == 0,
^~
>> drivers/staging//fwserial/dma_fifo.c:253:6: note: in expansion of macro 'FAIL'
if (FAIL(fifo, list_empty(&fifo->pending) != fifo->open == 0,
^~~~
vim +253 drivers/staging//fwserial/dma_fifo.c
236
237 /**
238 * dma_fifo_out_complete - marks pended dma as completed
239 * @fifo: address of in-place "struct dma_fifo" which was read from
240 * @complete: address of structure for previously pended dma to mark completed
241 */
242 int dma_fifo_out_complete(struct dma_fifo *fifo, struct dma_pending *complete)
243 {
244 struct dma_pending *pending, *next, *tmp;
245
246 if (!fifo->data)
247 return -ENOENT;
248 if (fifo->corrupt)
249 return -ENXIO;
250 if (list_empty(&fifo->pending) && fifo->open == 0)
251 return -EINVAL;
252
> 253 if (FAIL(fifo, list_empty(&fifo->pending) != fifo->open == 0,
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 41281 bytes --]
prev parent reply other threads:[~2018-02-02 2:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 5:39 Quytelda Kahja
2018-02-01 8:23 ` Dan Carpenter
2018-02-02 2:14 ` kbuild test robot [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=201802021052.heNR0okL%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quytelda@tamalin.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
all inboxes | Powered by JetHome®