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, rajsekhar.chundru@broadcom.com,
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 4/6] mpi3mr: Trigger support
Date: Wed, 15 May 2024 20:03:21 +0800 [thread overview]
Message-ID: <202405151955.BiAWI1SY-lkp@intel.com> (raw)
In-Reply-To: <20240514142858.51992-5-ranjan.kumar@broadcom.com>
Hi Ranjan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on mkp-scsi/for-next]
[also build test WARNING on jejb-scsi/for-next linus/master next-20240515]
[cannot apply to v6.9]
[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/mpi3mr-HDB-allocation-and-posting-for-hardware-and-Firmware-buffers/20240514-223346
base: https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git for-next
patch link: https://lore.kernel.org/r/20240514142858.51992-5-ranjan.kumar%40broadcom.com
patch subject: [PATCH v1 4/6] mpi3mr: Trigger support
config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20240515/202405151955.BiAWI1SY-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240515/202405151955.BiAWI1SY-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/202405151955.BiAWI1SY-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/scsi/mpi3mr/mpi3mr_app.c:717: warning: Function parameter or struct member 'trigger_data' not described in 'mpi3mr_set_trigger_data_in_hdb'
drivers/scsi/mpi3mr/mpi3mr_app.c:717: warning: Excess function parameter 'data' description in 'mpi3mr_set_trigger_data_in_hdb'
>> drivers/scsi/mpi3mr/mpi3mr_app.c:743: warning: Function parameter or struct member 'trigger_data' not described in 'mpi3mr_set_trigger_data_in_all_hdb'
>> drivers/scsi/mpi3mr/mpi3mr_app.c:743: warning: Excess function parameter 'data' description in 'mpi3mr_set_trigger_data_in_all_hdb'
vim +743 drivers/scsi/mpi3mr/mpi3mr_app.c
726
727 /**
728 * mpi3mr_set_trigger_data_in_all_hdb - Updates HDB trigger type
729 * and trigger data for all HDB
730 *
731 * @mrioc: Adapter instance reference
732 * @type: Trigger type
733 * @data: Trigger data
734 * @force: Trigger overwrite flag
735 *
736 * Updates trigger type and trigger data based on parameter
737 * passed to this function
738 *
739 * Return: Nothing
740 */
741 void mpi3mr_set_trigger_data_in_all_hdb(struct mpi3mr_ioc *mrioc,
742 u8 type, union mpi3mr_trigger_data *trigger_data, bool force)
> 743 {
744 struct diag_buffer_desc *hdb = NULL;
745
746 hdb = mpi3mr_diag_buffer_for_type(mrioc, MPI3_DIAG_BUFFER_TYPE_TRACE);
747 if (hdb)
748 mpi3mr_set_trigger_data_in_hdb(hdb, type, trigger_data, force);
749 hdb = mpi3mr_diag_buffer_for_type(mrioc, MPI3_DIAG_BUFFER_TYPE_FW);
750 if (hdb)
751 mpi3mr_set_trigger_data_in_hdb(hdb, type, trigger_data, force);
752 }
753
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-05-15 12:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 14:28 [PATCH v1 0/6] mpi3mr: Host diag buffer support Ranjan Kumar
2024-05-14 14:28 ` [PATCH v1 1/6] mpi3mr: HDB allocation and posting for hardware and Firmware buffers Ranjan Kumar
2024-05-15 9:58 ` kernel test robot
2024-05-14 14:28 ` [PATCH v1 2/6] mpi3mr: Driver buffer allocation and posting Ranjan Kumar
2024-05-14 14:28 ` [PATCH v1 3/6] mpi3mr: Dump driver and dmesg logs into driver diag buffer Ranjan Kumar
2024-05-15 11:00 ` kernel test robot
2024-05-14 14:28 ` [PATCH v1 4/6] mpi3mr: Trigger support Ranjan Kumar
2024-05-15 12:03 ` kernel test robot [this message]
2024-05-14 14:28 ` [PATCH v1 5/6] mpi3mr: Ioctl support for HDB Ranjan Kumar
2024-05-14 14:28 ` [PATCH v1 6/6] mpi3mr: Update driver version to 8.9.1.0.50 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=202405151955.BiAWI1SY-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=rajsekhar.chundru@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