From: kbuild test robot <lkp@intel.com>
To: Gabriel Beauchamp <beauchampgabriel@gmail.com>
Cc: kbuild-all@01.org, gregkh@linuxfoundation.org,
christian.gromm@microchip.com, colin.king@canonical.com,
gustavo@embeddedor.com, joe@perches.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Gabriel Beauchamp <beauchampgabriel@gmail.com>
Subject: Re: [PATCH v3] Staging: most: fix coding style issues
Date: Tue, 2 Jul 2019 01:40:50 +0800 [thread overview]
Message-ID: <201907020151.4hvM1eTo%lkp@intel.com> (raw)
In-Reply-To: <20190630165604.2452-1-beauchampgabriel@gmail.com>
Hi Gabriel,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on staging/staging-testing]
[also build test WARNING on v5.2-rc6 next-20190625]
[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/Gabriel-Beauchamp/Staging-most-fix-coding-style-issues/20190701-203804
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-rc1-7-g2b96cd8-dirty
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
vim +308 drivers/staging/most/core.c
296
297 static ssize_t set_datatype_show(struct device *dev,
298 struct device_attribute *attr,
299 char *buf)
300 {
301 int i;
302 char *type = "unconfigured\n";
303
304 struct most_channel *c = to_channel(dev);
305
306 for (i = 0; i < ARRAY_SIZE(ch_data_type); i++) {
307 if (c->cfg.data_type & ch_data_type[i].most_ch_data_type) {
> 308 type = ch_data_type[i].name;
309 break;
310 }
311 }
312 return snprintf(buf, PAGE_SIZE, "%s", type);
313 }
314
---
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-07-01 17:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-29 23:44 [PATCH] Staging: most: fix coding style issues Gabriel Beauchamp
2019-06-29 23:58 ` Joe Perches
2019-06-30 15:27 ` [PATCH v2] " Gabriel Beauchamp
2019-06-30 16:56 ` [PATCH v3] " Gabriel Beauchamp
2019-07-01 13:41 ` kbuild test robot
2019-07-01 17:40 ` kbuild test robot [this message]
2019-07-02 12:24 ` [PATCH v4] " Gabriel Beauchamp
2019-07-02 12:28 ` Greg KH
2019-07-23 13:43 ` [PATCH v3] " kbuild test robot
2019-08-08 14:23 ` kbuild test robot
2019-07-01 6:48 ` [PATCH v2] " Greg KH
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=201907020151.4hvM1eTo%lkp@intel.com \
--to=lkp@intel.com \
--cc=beauchampgabriel@gmail.com \
--cc=christian.gromm@microchip.com \
--cc=colin.king@canonical.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=gustavo@embeddedor.com \
--cc=joe@perches.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.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).