From: kernel test robot <lkp@intel.com>
To: Ranjan Kumar <ranjan.kumar@broadcom.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Sathya Prakash <sathya.prakash@broadcom.com>
Subject: drivers/scsi/mpi3mr/mpi3mr_app.c:461: warning: Excess function parameter 'data' description in 'mpi3mr_set_trigger_data_in_hdb'
Date: Sat, 18 Jan 2025 19:46:34 +0800 [thread overview]
Message-ID: <202501181924.hvKEeXDf-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 595523945be0a5a2f12a1c04772383293fbc04a1
commit: fc4444941140c80088102b39eb130d2a7a048e58 scsi: mpi3mr: HDB allocation and posting for hardware and firmware buffers
date: 7 months ago
config: arc-randconfig-r004-20221209 (https://download.01.org/0day-ci/archive/20250118/202501181924.hvKEeXDf-lkp@intel.com/config)
compiler: arc-elf-gcc (GCC) 12.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250118/202501181924.hvKEeXDf-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/202501181924.hvKEeXDf-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/scsi/mpi3mr/mpi3mr_app.c:461: warning: Excess function parameter 'data' description in 'mpi3mr_set_trigger_data_in_hdb'
vim +461 drivers/scsi/mpi3mr/mpi3mr_app.c
443
444 /**
445 * mpi3mr_set_trigger_data_in_hdb - Updates HDB trigger type and
446 * trigger data
447 *
448 * @hdb: HDB pointer
449 * @type: Trigger type
450 * @data: Trigger data
451 * @force: Trigger overwrite flag
452 * @trigger_data: pointer to trigger data information
453 *
454 * Updates trigger type and trigger data based on parameter
455 * passed to this function
456 *
457 * Return: Nothing
458 */
459 void mpi3mr_set_trigger_data_in_hdb(struct diag_buffer_desc *hdb,
460 u8 type, union mpi3mr_trigger_data *trigger_data, bool force)
> 461 {
462 if ((!force) && (hdb->trigger_type != MPI3MR_HDB_TRIGGER_TYPE_UNKNOWN))
463 return;
464 hdb->trigger_type = type;
465 if (!trigger_data)
466 memset(&hdb->trigger_data, 0, sizeof(*trigger_data));
467 else
468 memcpy(&hdb->trigger_data, trigger_data, sizeof(*trigger_data));
469 }
470
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-01-18 11:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202501181924.hvKEeXDf-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ranjan.kumar@broadcom.com \
--cc=sathya.prakash@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
all inboxes | Powered by JetHome®