From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: drivers/iio/chemical/scd4x.c:482:0: warning: syntax error [syntaxError]
Date: Tue, 25 Jan 2022 03:23:21 +0800 [thread overview]
Message-ID: <202201250128.YEbVeyuR-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1297 bytes --]
CC: kbuild-all(a)lists.01.org
CC: linux-kernel(a)vger.kernel.org
TO: Roan van Dijk <roan@protonic.nl>
CC: Jonathan Cameron <Jonathan.Cameron@huawei.com>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: dd81e1c7d5fb126e5fbc5c9e334d7b3ec29a16a0
commit: 49d22b695cbb690b1d1a9d21b61eaf8f61a525d4 drivers: iio: chemical: Add support for Sensirion SCD4x CO2 sensor
date: 3 months ago
:::::: branch date: 26 hours ago
:::::: commit date: 3 months ago
compiler: sparc64-linux-gcc (GCC) 11.2.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
cppcheck possible warnings: (new ones prefixed by >>, may not real problems)
>> drivers/iio/chemical/scd4x.c:482:0: warning: syntax error [syntaxError]
^
vim +482 drivers/iio/chemical/scd4x.c
49d22b695cbb69 Roan van Dijk 2021-10-08 480
49d22b695cbb69 Roan van Dijk 2021-10-08 481 static IIO_CONST_ATTR(calibration_forced_value_available,
49d22b695cbb69 Roan van Dijk 2021-10-08 @482 __stringify([SCD4X_FRC_MIN_PPM 1 SCD4X_FRC_MAX_PPM]));
49d22b695cbb69 Roan van Dijk 2021-10-08 483
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
next reply other threads:[~2022-01-24 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 19:23 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-21 3:02 drivers/iio/chemical/scd4x.c:482:0: warning: syntax error [syntaxError] kernel test robot
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=202201250128.YEbVeyuR-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild@lists.01.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 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.