From: kbuild test robot <lkp@intel.com>
To: Daniel Campello <campello@chromium.org>
Cc: kbuild-all@01.org, LKML <linux-kernel@vger.kernel.org>,
Daniel Campello <campello@chromium.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Benson Leung <bleung@chromium.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Duncan Laurie <dlaurie@google.com>,
Nick Crews <ncrews@chromium.org>
Subject: Re: [PATCH v2] platform/chrome: wilco_ec: Add debugfs test_event file
Date: Wed, 18 Sep 2019 07:49:08 +0800 [thread overview]
Message-ID: <201909180722.Rq0b1WMA%lkp@intel.com> (raw)
In-Reply-To: <20190917215752.67391-1-campello@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 2371 bytes --]
Hi Daniel,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[cannot apply to v5.3 next-20190916]
[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/Daniel-Campello/platform-chrome-wilco_ec-Add-debugfs-test_event-file/20190918-055910
config: x86_64-allmodconfig (attached as .config)
compiler: gcc-7 (Debian 7.4.0-11) 7.4.0
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
In file included from drivers/platform/chrome/wilco_ec/debugfs.c:11:0:
drivers/platform/chrome/wilco_ec/debugfs.c: In function 'fops_test_event_open':
>> include/linux/debugfs.h:43:56: warning: too many arguments for format [-Wformat-extra-args]
static int __fops ## _open(struct inode *inode, struct file *file) \
^
>> drivers/platform/chrome/wilco_ec/debugfs.c:230:1: note: in expansion of macro 'DEFINE_DEBUGFS_ATTRIBUTE'
DEFINE_DEBUGFS_ATTRIBUTE(fops_test_event, NULL, test_event_set, NULL);
^~~~~~~~~~~~~~~~~~~~~~~~
--
In file included from drivers/platform//chrome/wilco_ec/debugfs.c:11:0:
drivers/platform//chrome/wilco_ec/debugfs.c: In function 'fops_test_event_open':
>> include/linux/debugfs.h:43:56: warning: too many arguments for format [-Wformat-extra-args]
static int __fops ## _open(struct inode *inode, struct file *file) \
^
drivers/platform//chrome/wilco_ec/debugfs.c:230:1: note: in expansion of macro 'DEFINE_DEBUGFS_ATTRIBUTE'
DEFINE_DEBUGFS_ATTRIBUTE(fops_test_event, NULL, test_event_set, NULL);
^~~~~~~~~~~~~~~~~~~~~~~~
vim +/DEFINE_DEBUGFS_ATTRIBUTE +230 drivers/platform/chrome/wilco_ec/debugfs.c
226
227 /* Format set to NULL since it is only used on read operations which are
228 * forbidden by file permissions.
229 */
> 230 DEFINE_DEBUGFS_ATTRIBUTE(fops_test_event, NULL, test_event_set, NULL);
231
---
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: 70298 bytes --]
prev parent reply other threads:[~2019-09-17 23:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 21:57 Daniel Campello
2019-09-17 23:49 ` 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=201909180722.Rq0b1WMA%lkp@intel.com \
--to=lkp@intel.com \
--cc=alexandre.belloni@bootlin.com \
--cc=bleung@chromium.org \
--cc=campello@chromium.org \
--cc=dlaurie@google.com \
--cc=enric.balletbo@collabora.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ncrews@chromium.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®