linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: kbuild-all@01.org, linux-block@vger.kernel.org,
	linux-leds@vger.kernel.org, linux-nvme@lists.infradead.org,
	linux-scsi@vger.kernel.org, Akinobu Mita <akinobu.mita@gmail.com>,
	Frank Steiner <fsteiner-mail1@bio.ifi.lmu.de>,
	Jacek Anaszewski <jacek.anaszewski@gmail.com>,
	Pavel Machek <pavel@ucw.cz>, Dan Murphy <dmurphy@ti.com>,
	Jens Axboe <axboe@kernel.dk>,
	"James E.J. Bottomley" <jejb@linux.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH v2 1/3] block: introduce LED block device activity trigger
Date: Tue, 23 Jul 2019 10:04:23 +0800	[thread overview]
Message-ID: <201907231015.ELtC6gvZ%lkp@intel.com> (raw)
In-Reply-To: <1563807552-23498-2-git-send-email-akinobu.mita@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2122 bytes --]

Hi Akinobu,

I love your patch! Yet something to improve:

[auto build test ERROR on linus/master]
[also build test ERROR on v5.3-rc1 next-20190722]
[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/Akinobu-Mita/block-introduce-LED-block-device-activity-trigger/20190723-074956
config: x86_64-fedora-25 (attached as .config)
compiler: gcc-7 (Debian 7.4.0-10) 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 error/warnings (new ones prefixed by >>):

   In file included from drivers/block/umem.c:52:0:
>> drivers/block/umem.h:39:19: error: expected identifier before numeric constant
    #define  LED_OFF  0x00
                      ^
>> include/linux/leds.h:27:2: note: in expansion of macro 'LED_OFF'
     LED_OFF  = 0,
     ^~~~~~~

vim +/LED_OFF +27 include/linux/leds.h

af410fc1 Johannes Berg  2006-09-29  19  
c72a1d60 Richard Purdie 2006-03-31  20  struct device;
5fd752b6 Baolin Wang    2018-10-11  21  struct led_pattern;
c72a1d60 Richard Purdie 2006-03-31  22  /*
c72a1d60 Richard Purdie 2006-03-31  23   * LED Core
c72a1d60 Richard Purdie 2006-03-31  24   */
c72a1d60 Richard Purdie 2006-03-31  25  
c72a1d60 Richard Purdie 2006-03-31  26  enum led_brightness {
c72a1d60 Richard Purdie 2006-03-31 @27  	LED_OFF		= 0,
4e552c8c Andi Shyti     2017-01-05  28  	LED_ON		= 1,
c72a1d60 Richard Purdie 2006-03-31  29  	LED_HALF	= 127,
c72a1d60 Richard Purdie 2006-03-31  30  	LED_FULL	= 255,
c72a1d60 Richard Purdie 2006-03-31  31  };
c72a1d60 Richard Purdie 2006-03-31  32  

:::::: The code at line 27 was first introduced by commit
:::::: c72a1d608dd0eb3d553a08bfdf1c0041bebaa8a0 [PATCH] LED: add LED class

:::::: TO: Richard Purdie <rpurdie@rpsys.net>
:::::: CC: Linus Torvalds <torvalds@g5.osdl.org>

---
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: 50846 bytes --]

  reply	other threads:[~2019-07-23  2:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-22 14:59 [PATCH v2 0/3] introduce LED block device activity trigger Akinobu Mita
2019-07-22 14:59 ` [PATCH v2 1/3] block: " Akinobu Mita
2019-07-23  2:04   ` kbuild test robot [this message]
2019-07-23 15:26     ` Akinobu Mita
2019-07-23  2:22   ` kbuild test robot
2019-07-23 15:28     ` Akinobu Mita
2019-07-26 21:22   ` Jacek Anaszewski
2019-07-28 13:51     ` Akinobu Mita
2019-07-28 17:46       ` Jacek Anaszewski
2019-07-22 14:59 ` [PATCH v2 2/3] ledtrig-blk: add interface to stop and restart polling disk stats Akinobu Mita
2019-07-22 14:59 ` [PATCH v2 3/3] scsi: sd: stop polling disk stats by ledtrig-blk during runtime suspend Akinobu Mita
2019-08-10 15:41 ` [PATCH v2 0/3] introduce LED block device activity trigger Frank Steiner

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=201907231015.ELtC6gvZ%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akinobu.mita@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=dmurphy@ti.com \
    --cc=fsteiner-mail1@bio.ifi.lmu.de \
    --cc=jacek.anaszewski@gmail.com \
    --cc=jejb@linux.ibm.com \
    --cc=kbuild-all@01.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=pavel@ucw.cz \
    /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).