From: sashiko-bot@kernel.org
To: "Adrián García Casado" <adriangarciacasado42@gmail.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi: qedi: Add __printf to debug helpers and fix format strings
Date: Mon, 09 Nov 2026 14:29:50 +0000 [thread overview]
Message-ID: <sashiko-outbox-205105@kernel.org> (raw)
In-Reply-To: <20261109141738.1624579-1-adriangarciacasado42@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Medium] scsi: qedi: -Wformat build error in
qedi_alloc_nvm_iscsi_cfg() on 32-bit DMA
--
commit dbd61cf20f660a9013f24529bb4ce72d39dfb22d
Author: Adrián García Casado <adriangarciacasado42@gmail.com>
scsi: qedi: Add __printf to debug helpers and fix format strings
This commit adds __printf() attributes to the qedi_dbg_*() logging helpers
and updates format strings in qedi_fw.c and qedi_main.c to match their
argument types.
> diff --git a/drivers/scsi/qedi/qedi_dbg.h b/drivers/scsi/qedi/qedi_dbg.h
> index 8649518658691..70acb55847f4f 100644
> --- a/drivers/scsi/qedi/qedi_dbg.h
> +++ b/drivers/scsi/qedi/qedi_dbg.h
> @@ -78,12 +78,16 @@ struct qedi_dbg_ctx {
> qedi_dbg_info(pdev, __func__, __LINE__, level, fmt, \
> ## __VA_ARGS__)
>
> +__printf(4, 5)
> void qedi_dbg_err(struct qedi_dbg_ctx *qedi, const char *func, u32 line,
> const char *fmt, ...);
> +__printf(4, 5)
> void qedi_dbg_warn(struct qedi_dbg_ctx *qedi, const char *func, u32 line,
> const char *fmt, ...);
> +__printf(4, 5)
> void qedi_dbg_notice(struct qedi_dbg_ctx *qedi, const char *func, u32 line,
> const char *fmt, ...);
> +__printf(5, 6)
> void qedi_dbg_info(struct qedi_dbg_ctx *qedi, const char *func, u32 line,
> u32 info, const char *fmt, ...);
[Severity: Medium]
Does adding __printf(5, 6) to qedi_dbg_info() cause a -Wformat build
regression in qedi_alloc_nvm_iscsi_cfg() when CONFIG_ARCH_DMA_ADDR_T_64BIT
is not set?
drivers/scsi/qedi/qedi_main.c:qedi_alloc_nvm_iscsi_cfg() {
...
QEDI_INFO(&qedi->dbg_ctx, QEDI_LOG_INFO,
"NVM BUF addr=0x%p dma=0x%llx.\n", qedi->iscsi_image,
qedi->nvm_buf_dma);
...
}
qedi->nvm_buf_dma is a dma_addr_t, which is u32 on 32-bit DMA
configurations, so formatting it with 0x%llx instead of %pad (passing
&qedi->nvm_buf_dma) triggers a format warning and breaks CONFIG_WERROR=y
builds.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261109141738.1624579-1-adriangarciacasado42@gmail.com?part=1
next prev parent reply other threads:[~2026-11-09 14:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 14:17 [PATCH] scsi: qedi: Add __printf to debug helpers and fix format strings Adrián García Casado
2026-11-09 14:29 ` sashiko-bot [this message]
2026-11-09 22:50 ` kernel test robot
2026-11-10 0:35 ` kernel test robot
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=sashiko-outbox-205105@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=adriangarciacasado42@gmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=sashiko-reviews@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.