From: kernel test robot <lkp@intel.com>
To: Ranjan Kumar <ranjan.kumar@broadcom.com>,
linux-scsi@vger.kernel.org, martin.petersen@oracle.com
Cc: oe-kbuild-all@lists.linux.dev, sathya.prakash@broadcom.com,
sumit.saxena@broadcom.com, chandrakanth.patil@broadcom.com,
prayas.patel@broadcom.com,
Ranjan Kumar <ranjan.kumar@broadcom.com>
Subject: Re: [PATCH v1 1/5] mpt3sas: Added no_turs flag to device unblock logic
Date: Fri, 31 Oct 2025 02:48:30 +0800 [thread overview]
Message-ID: <202510310216.gerpzbxP-lkp@intel.com> (raw)
In-Reply-To: <20251029181058.39157-2-ranjan.kumar@broadcom.com>
Hi Ranjan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on jejb-scsi/for-next]
[also build test WARNING on mkp-scsi/for-next linus/master v6.18-rc3 next-20251030]
[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/Ranjan-Kumar/mpt3sas-Added-no_turs-flag-to-device-unblock-logic/20251030-025730
base: https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git for-next
patch link: https://lore.kernel.org/r/20251029181058.39157-2-ranjan.kumar%40broadcom.com
patch subject: [PATCH v1 1/5] mpt3sas: Added no_turs flag to device unblock logic
config: i386-randconfig-054-20251030 (https://download.01.org/0day-ci/archive/20251031/202510310216.gerpzbxP-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251031/202510310216.gerpzbxP-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/202510310216.gerpzbxP-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: drivers/scsi/mpt3sas/mpt3sas_scsih.c:3832 function parameter 'no_turs' not described in '_scsih_ublock_io_all_device'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-10-30 18:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 18:10 [PATCH v1 0/5] mpt3sas: Improve device readiness handling and event recovery Ranjan Kumar
2025-10-29 18:10 ` [PATCH v1 1/5] mpt3sas: Added no_turs flag to device unblock logic Ranjan Kumar
2025-10-30 18:48 ` kernel test robot [this message]
2025-10-29 18:10 ` [PATCH v1 2/5] mpt3sas: Added issue_scsi_cmd_to_bringup_drive module parameter part-1 Ranjan Kumar
2025-10-29 18:10 ` [PATCH v1 3/5] mpt3sas: improve device discovery and readiness handling for slow devices part-2 Ranjan Kumar
2025-10-31 1:49 ` kernel test robot
2025-10-29 18:10 ` [PATCH v1 4/5] mpt3sas: Add firmware event requeue support for busy devices Ranjan Kumar
2025-10-31 9:28 ` kernel test robot
2025-10-29 18:10 ` [PATCH v1 5/5] mpt3sas: Add configurable command retry limit for slow-to-respond devices Ranjan Kumar
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=202510310216.gerpzbxP-lkp@intel.com \
--to=lkp@intel.com \
--cc=chandrakanth.patil@broadcom.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=prayas.patel@broadcom.com \
--cc=ranjan.kumar@broadcom.com \
--cc=sathya.prakash@broadcom.com \
--cc=sumit.saxena@broadcom.com \
/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