From: kernel test robot <lkp@intel.com>
To: kensanya@163.com, martin.petersen@oracle.com
Cc: oe-kbuild-all@lists.linux.dev, linux-scsi@vger.kernel.org,
target-devel@vger.kernel.org, TanZheng <tanzheng@kylinos.cn>
Subject: Re: [PATCH] target/stat: implement scsiPortBusyStatuses counter
Date: Wed, 5 Aug 2026 11:47:29 +0800 [thread overview]
Message-ID: <202608051155.lyM6hfgB-lkp@intel.com> (raw)
In-Reply-To: <20260708093433.838647-1-kensanya@163.com>
Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on mkp-scsi/for-next]
[also build test WARNING on linus/master v7.2-rc6 next-20260804]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/kensanya-163-com/target-stat-implement-scsiPortBusyStatuses-counter/20260805-032126
base: https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git for-next
patch link: https://lore.kernel.org/r/20260708093433.838647-1-kensanya%40163.com
patch subject: [PATCH] target/stat: implement scsiPortBusyStatuses counter
config: s390-randconfig-001-20260805 (https://download.01.org/0day-ci/archive/20260805/202608051155.lyM6hfgB-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260805/202608051155.lyM6hfgB-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202608051155.lyM6hfgB-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/target/target_core_stat.c: Assembler messages:
>> drivers/target/target_core_stat.c:49: Warning: missing closing `"'
>> drivers/target/target_core_stat.c:49: Warning: missing closing `"'
>> drivers/target/target_core_stat.c:49: Warning: missing closing `"'
>> drivers/target/target_core_stat.c:49: Warning: missing closing `"'
>> drivers/target/target_core_stat.c:49: Warning: missing closing `"'
>> drivers/target/target_core_stat.c:49: Warning: missing closing `"'
>> drivers/target/target_core_stat.c:49: Warning: missing closing `"'
>> drivers/target/target_core_stat.c:49: Warning: missing closing `"'
>> drivers/target/target_core_stat.c:49: Warning: missing closing `"'
>> drivers/target/target_core_stat.c:49: Warning: missing closing `"'
>> drivers/target/target_core_stat.c:49: Warning: missing closing `"'
>> drivers/target/target_core_stat.c:49: Warning: missing closing `"'
>> drivers/target/target_core_stat.c:49: Warning: missing closing `"'
>> drivers/target/target_core_stat.c:49: Warning: missing closing `"'
>> drivers/target/target_core_stat.c:49: Warning: missing closing `"'
>> drivers/target/target_core_stat.c:49: Warning: missing closing `"'
>> drivers/target/target_core_stat.c:49: Warning: missing closing `"'
drivers/target/target_core_stat.c:54: Warning: missing closing `"'
drivers/target/target_core_stat.c:54: Warning: missing closing `"'
drivers/target/target_core_stat.c:54: Warning: missing closing `"'
drivers/target/target_core_stat.c:54: Warning: missing closing `"'
drivers/target/target_core_stat.c:54: Warning: missing closing `"'
drivers/target/target_core_stat.c:54: Warning: missing closing `"'
drivers/target/target_core_stat.c:54: Warning: missing closing `"'
drivers/target/target_core_stat.c:54: Warning: missing closing `"'
drivers/target/target_core_stat.c:54: Warning: missing closing `"'
drivers/target/target_core_stat.c:54: Warning: missing closing `"'
drivers/target/target_core_stat.c:54: Warning: missing closing `"'
drivers/target/target_core_stat.c:54: Warning: missing closing `"'
drivers/target/target_core_stat.c:54: Warning: missing closing `"'
drivers/target/target_core_stat.c:54: Warning: missing closing `"'
drivers/target/target_core_stat.c:54: Warning: missing closing `"'
drivers/target/target_core_stat.c:54: Warning: missing closing `"'
drivers/target/target_core_stat.c:54: Warning: missing closing `"'
vim +49 drivers/target/target_core_stat.c
12d233842987d9 Nicholas Bellinger 2011-03-14 @49
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-08-05 3:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 9:34 [PATCH] target/stat: implement scsiPortBusyStatuses counter kensanya
2026-07-08 9:57 ` sashiko-bot
2026-07-09 6:29 ` kensanya
2026-08-05 3:47 ` kernel 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=202608051155.lyM6hfgB-lkp@intel.com \
--to=lkp@intel.com \
--cc=kensanya@163.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tanzheng@kylinos.cn \
--cc=target-devel@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