From: kernel test robot <lkp@intel.com>
To: Anastasia Kovaleva <a.kovaleva@yadro.com>,
martin.petersen@oracle.com, bootc@bootc.net,
bostroesser@gmail.com, michael.christie@oracle.com
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-scsi@vger.kernel.org, target-devel@vger.kernel.org,
linux@yadro.com
Subject: Re: [PATCH 08/10] target: core: Use extended logs where possible
Date: Sat, 30 Nov 2024 06:08:21 +0800 [thread overview]
Message-ID: <202411300554.nCMgLGMh-lkp@intel.com> (raw)
In-Reply-To: <20241129153056.6985-9-a.kovaleva@yadro.com>
Hi Anastasia,
kernel test robot noticed the following build warnings:
[auto build test WARNING on mkp-scsi/for-next]
[also build test WARNING on linus/master next-20241128]
[cannot apply to v6.12]
[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/Anastasia-Kovaleva/target-core-Improve-SCSI-target-logs/20241129-234412
base: https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git for-next
patch link: https://lore.kernel.org/r/20241129153056.6985-9-a.kovaleva%40yadro.com
patch subject: [PATCH 08/10] target: core: Use extended logs where possible
config: arm64-randconfig-003-20241130 (https://download.01.org/0day-ci/archive/20241130/202411300554.nCMgLGMh-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241130/202411300554.nCMgLGMh-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/202411300554.nCMgLGMh-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/target/target_core_pr.c:64:26: warning: unused variable 'pr_register_type_table_str' [-Wunused-const-variable]
64 | static const char *const pr_register_type_table_str[] = {
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/target/target_core_pr.c:75:26: warning: unused variable 'pr_preempt_type_table_str' [-Wunused-const-variable]
75 | static const char *const pr_preempt_type_table_str[] = {
| ^~~~~~~~~~~~~~~~~~~~~~~~~
2 warnings generated.
vim +/pr_register_type_table_str +64 drivers/target/target_core_pr.c
63
> 64 static const char *const pr_register_type_table_str[] = {
65 "REGISTER",
66 "REGISTER_AND_IGNORE_EXISTING_KEY",
67 "REGISTER_AND_MOVE",
68 };
69
70 enum preempt_type {
71 PREEMPT,
72 PREEMPT_AND_ABORT,
73 };
74
> 75 static const char *const pr_preempt_type_table_str[] = {
76 "PREEMPT",
77 "PREEMPT_AND_ABORT",
78 };
79
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-11-29 22:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 15:30 [PATCH 00/10] Improve SCSI target logs Anastasia Kovaleva
2024-11-29 15:30 ` [PATCH 01/10] target: core: " Anastasia Kovaleva
2024-11-29 15:30 ` [PATCH 02/10] target: Use new log wrappers Anastasia Kovaleva
2024-11-29 15:30 ` [PATCH 03/10] target: Fix quoted strings splitting Anastasia Kovaleva
2024-11-29 15:30 ` [PATCH 04/10] target: Fix some obvious style problems Anastasia Kovaleva
2024-11-29 15:30 ` [PATCH 05/10] target: Add log prefix to all tcm files Anastasia Kovaleva
2024-11-29 15:30 ` [PATCH 06/10] target: Remove old prefixes from log messages Anastasia Kovaleva
2024-11-29 15:30 ` [PATCH 07/10] target: core: Extend CaW logging Anastasia Kovaleva
2024-11-29 15:30 ` [PATCH 08/10] target: core: Use extended logs where possible Anastasia Kovaleva
2024-11-29 21:05 ` kernel test robot
2024-11-29 22:08 ` kernel test robot [this message]
2024-11-29 15:30 ` [PATCH 09/10] target: Use __func__ in logs Anastasia Kovaleva
2024-11-29 15:30 ` [PATCH 10/10] target: iscsi: Improve a log message Anastasia Kovaleva
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=202411300554.nCMgLGMh-lkp@intel.com \
--to=lkp@intel.com \
--cc=a.kovaleva@yadro.com \
--cc=bootc@bootc.net \
--cc=bostroesser@gmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@yadro.com \
--cc=llvm@lists.linux.dev \
--cc=martin.petersen@oracle.com \
--cc=michael.christie@oracle.com \
--cc=oe-kbuild-all@lists.linux.dev \
--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