mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 v3] platform/chrome: wilco_ec: Add debugfs test_event file
Date: Thu, 19 Sep 2019 04:11:20 +0800	[thread overview]
Message-ID: <201909190423.JhgaSYXg%lkp@intel.com> (raw)
In-Reply-To: <20190918173707.129462-1-campello@chromium.org>

[-- Attachment #1: Type: text/plain, Size: 1877 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-20190917]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Daniel-Campello/platform-chrome-wilco_ec-Add-debugfs-test_event-file/20190919-014111
config: x86_64-allyesconfig (attached as .config)
compiler: gcc-7 (Debian 7.4.0-13) 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':
>> drivers/platform/chrome/wilco_ec/debugfs.c:230:65: warning: zero-length gnu_printf format string [-Wformat-zero-length]
    DEFINE_DEBUGFS_ATTRIBUTE(fops_test_event, NULL, test_event_set, "");
                                                                    ^
   include/linux/debugfs.h:45:29: note: in definition of macro 'DEFINE_DEBUGFS_ATTRIBUTE'
     __simple_attr_check_format(__fmt, 0ull);   \
                                ^~~~~

vim +230 drivers/platform/chrome/wilco_ec/debugfs.c

   226	
   227	/* Format is empty 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, "");
   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: 69757 bytes --]

      reply	other threads:[~2019-09-18 20:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-18 17:37 Daniel Campello
2019-09-18 20:11 ` 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=201909190423.JhgaSYXg%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®