From: Frank Li <Frank.li@oss.nxp.com>
To: Rosen Penev <rosenp@gmail.com>
Cc: dmaengine@vger.kernel.org, Vinod Koul <vkoul@kernel.org>,
Frank Li <Frank.Li@kernel.org>, Yuri Tikhonov <yur@emcraft.com>,
Anatolij Gustschin <agust@denx.de>,
Dan Williams <djbw@kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dmaengine: ppc4xx: fix format specifiers for size_t arguments
Date: Fri, 11 Sep 2026 10:49:29 -0500 [thread overview]
Message-ID: <aqQjCdMSalzM91VT@SMW015318> (raw)
In-Reply-To: <20260910211440.65618-1-rosenp@gmail.com>
On Thu, Sep 10, 2026 at 02:14:40PM -0700, Rosen Penev wrote:
dmaengine: ppc4xx: change to %zu format specifiers for size_t arguments.
Frank
> Several dev_err, dev_dbg, pr_debug, and printk calls use %d or %u
> format specifiers for size_t arguments (len, pool_size). Fix them
> to use %zu to avoid warnings on 64-bit builds.
>
> Fixes: 12458ea06efd7 ("ppc440spe-adma: adds updated ppc440spe adma driver")
> Assisted-by: opencode:big-pickle
> Signed-off-by: Rosen Penev <rosenp@gmail.com>
> ---
> drivers/dma/ppc4xx/adma.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/dma/ppc4xx/adma.c b/drivers/dma/ppc4xx/adma.c
> index 279a431ccae3..bcc54d584e2b 100644
> --- a/drivers/dma/ppc4xx/adma.c
> +++ b/drivers/dma/ppc4xx/adma.c
> @@ -799,7 +799,7 @@ static int ppc440spe_chan_xor_slot_count(size_t len, int src_cnt,
> if (likely(len <= PPC440SPE_ADMA_XOR_MAX_BYTE_COUNT))
> return slot_cnt;
>
> - printk(KERN_ERR "%s: len %d > max %d !!\n",
> + printk(KERN_ERR "%s: len %zu > max %d !!\n",
> __func__, len, PPC440SPE_ADMA_XOR_MAX_BYTE_COUNT);
> BUG();
> return slot_cnt;
> @@ -1989,7 +1989,7 @@ static struct dma_async_tx_descriptor *ppc440spe_adma_prep_dma_memcpy(
> spin_lock_bh(&ppc440spe_chan->lock);
>
> dev_dbg(ppc440spe_chan->device->common.dev,
> - "ppc440spe adma%d: %s len: %u int_en %d\n",
> + "ppc440spe adma%d: %s len: %zu int_en %d\n",
> ppc440spe_chan->device->id, __func__, len,
> flags & DMA_PREP_INTERRUPT ? 1 : 0);
> slot_cnt = slots_per_op = 1;
> @@ -2030,7 +2030,7 @@ static struct dma_async_tx_descriptor *ppc440spe_adma_prep_dma_xor(
> BUG_ON(len > PPC440SPE_ADMA_XOR_MAX_BYTE_COUNT);
>
> dev_dbg(ppc440spe_chan->device->common.dev,
> - "ppc440spe adma%d: %s src_cnt: %d len: %u int_en: %d\n",
> + "ppc440spe adma%d: %s src_cnt: %d len: %zu int_en: %d\n",
> ppc440spe_chan->device->id, __func__, src_cnt, len,
> flags & DMA_PREP_INTERRUPT ? 1 : 0);
>
> @@ -2279,7 +2279,7 @@ static struct ppc440spe_adma_desc_slot *ppc440spe_dma01_prep_pq(
> unsigned long op = 0;
> unsigned char mult = 1;
>
> - pr_debug("%s: dst_cnt %d, src_cnt %d, len %d\n",
> + pr_debug("%s: dst_cnt %d, src_cnt %d, len %zu\n",
> __func__, dst_cnt, src_cnt, len);
> /* select operations WXOR/RXOR depending on the
> * source addresses of operators and the number
> @@ -2553,7 +2553,7 @@ static struct dma_async_tx_descriptor *ppc440spe_adma_prep_dma_pq(
> BUG_ON(!dst_cnt);
>
> dev_dbg(ppc440spe_chan->device->common.dev,
> - "ppc440spe adma%d: %s src_cnt: %d len: %u int_en: %d\n",
> + "ppc440spe adma%d: %s src_cnt: %d len: %zu int_en: %d\n",
> ppc440spe_chan->device->id, __func__, src_cnt, len,
> flags & DMA_PREP_INTERRUPT ? 1 : 0);
>
> @@ -4077,7 +4077,7 @@ static int ppc440spe_adma_probe(struct platform_device *ofdev)
> adev->pool_size, &adev->dma_desc_pool,
> GFP_KERNEL);
> if (adev->dma_desc_pool_virt == NULL) {
> - dev_err(&ofdev->dev, "failed to allocate %d bytes of coherent "
> + dev_err(&ofdev->dev, "failed to allocate %zu bytes of coherent "
> "memory for hardware descriptors\n",
> adev->pool_size);
> initcode = PPC_ADMA_INIT_COHERENT;
> --
> 2.55.0
>
prev parent reply other threads:[~2026-09-11 15:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 21:14 Rosen Penev
2026-09-11 15:49 ` Frank Li [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=aqQjCdMSalzM91VT@SMW015318 \
--to=frank.li@oss.nxp.com \
--cc=Frank.Li@kernel.org \
--cc=agust@denx.de \
--cc=djbw@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rosenp@gmail.com \
--cc=vkoul@kernel.org \
--cc=yur@emcraft.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®