From: kernel test robot <lkp@intel.com>
To: "Adrián García Casado" <adriangarciacasado42@gmail.com>,
"Nilesh Javali" <njavali@marvell.com>,
"Manish Rangankar" <mrangankar@marvell.com>,
"Martin K . Petersen" <mkp@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
GR-ETH-Storage-Upstream@marvell.com,
"James E . J . Bottomley" <James.Bottomley@hansenpartnership.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
"Adrián García Casado" <adriangarciacasado42@gmail.com>
Subject: Re: [PATCH] scsi: qedi: Add __printf to debug helpers and fix format strings
Date: Tue, 10 Nov 2026 06:50:02 +0800 [thread overview]
Message-ID: <202611100645.IuoveOp3-lkp@intel.com> (raw)
In-Reply-To: <20261109141738.1624579-1-adriangarciacasado42@gmail.com>
Hi Adrián,
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 v7.4-rc2 next-20261109]
[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/Adri-n-Garc-a-Casado/scsi-qedi-Add-__printf-to-debug-helpers-and-fix-format-strings/20261109-151738
base: https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git for-next
patch link: https://lore.kernel.org/r/20261109141738.1624579-1-adriangarciacasado42%40gmail.com
patch subject: [PATCH] scsi: qedi: Add __printf to debug helpers and fix format strings
config: i386-randconfig-1002-20261109 (https://download.01.org/0day-ci/archive/20261110/202611100645.IuoveOp3-lkp@intel.com/config)
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261110/202611100645.IuoveOp3-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/202611100645.IuoveOp3-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/scsi/qedi/qedi_main.c:1489:5: warning: format specifies type 'unsigned long long' but the argument has type 'dma_addr_t' (aka 'unsigned int') [-Wformat]
1488 | "NVM BUF addr=0x%p dma=0x%llx.\n", qedi->iscsi_image,
| ~~~~
| %x
1489 | qedi->nvm_buf_dma);
| ^~~~~~~~~~~~~~~~~
drivers/scsi/qedi/qedi_dbg.h:79:13: note: expanded from macro 'QEDI_INFO'
78 | qedi_dbg_info(pdev, __func__, __LINE__, level, fmt, \
| ~~~
79 | ## __VA_ARGS__)
| ^~~~~~~~~~~
1 warning generated.
vim +1489 drivers/scsi/qedi/qedi_main.c
c57ec8fb7c0253 Nilesh Javali 2017-06-27 1477
c57ec8fb7c0253 Nilesh Javali 2017-06-27 1478 static int qedi_alloc_nvm_iscsi_cfg(struct qedi_ctx *qedi)
c57ec8fb7c0253 Nilesh Javali 2017-06-27 1479 {
750afb08ca7131 Luis Chamberlain 2019-01-04 1480 qedi->iscsi_image = dma_alloc_coherent(&qedi->pdev->dev,
872e192fab6438 Colin Ian King 2019-03-27 1481 sizeof(struct qedi_nvm_iscsi_image),
750afb08ca7131 Luis Chamberlain 2019-01-04 1482 &qedi->nvm_buf_dma, GFP_KERNEL);
c77a2fa3ff8f73 Nilesh Javali 2018-08-29 1483 if (!qedi->iscsi_image) {
c57ec8fb7c0253 Nilesh Javali 2017-06-27 1484 QEDI_ERR(&qedi->dbg_ctx, "Could not allocate NVM BUF.\n");
c57ec8fb7c0253 Nilesh Javali 2017-06-27 1485 return -ENOMEM;
c57ec8fb7c0253 Nilesh Javali 2017-06-27 1486 }
c57ec8fb7c0253 Nilesh Javali 2017-06-27 1487 QEDI_INFO(&qedi->dbg_ctx, QEDI_LOG_INFO,
c77a2fa3ff8f73 Nilesh Javali 2018-08-29 1488 "NVM BUF addr=0x%p dma=0x%llx.\n", qedi->iscsi_image,
c57ec8fb7c0253 Nilesh Javali 2017-06-27 @1489 qedi->nvm_buf_dma);
c57ec8fb7c0253 Nilesh Javali 2017-06-27 1490
c57ec8fb7c0253 Nilesh Javali 2017-06-27 1491 return 0;
c57ec8fb7c0253 Nilesh Javali 2017-06-27 1492 }
c57ec8fb7c0253 Nilesh Javali 2017-06-27 1493
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-11-09 22:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 14:17 Adrián García Casado
2026-11-09 22:50 ` 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=202611100645.IuoveOp3-lkp@intel.com \
--to=lkp@intel.com \
--cc=GR-ETH-Storage-Upstream@marvell.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=adriangarciacasado42@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mkp@kernel.org \
--cc=mrangankar@marvell.com \
--cc=njavali@marvell.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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®