From: Vinod Koul <vkoul@kernel.org>
To: dmaengine@vger.kernel.org, Linus Walleij <linus.walleij@linaro.org>
Cc: Vinod Koul <vkoul@kernel.org>,
linux-arm-kernel@lists.infradead.org,
kernel test robot <lkp@intel.com>
Subject: [PATCH 1/2] dmaengine: ste_dma40: use correct print specfier for resource_size_t
Date: Wed, 17 May 2023 12:14:33 +0530 [thread overview]
Message-ID: <20230517064434.141091-1-vkoul@kernel.org> (raw)
We should use %pR for printing resource_size_t, so update that fixing
the warning:
drivers/dma/ste_dma40.c:3556:25: warning: format specifies type 'unsigned int'
but the argument has type 'resource_size_t' (aka 'unsigned long long') [-Wformat]
Reported-by: kernel test robot <lkp@intel.com>
Fixes: 5a1a3b9c19dd ("dmaengine: ste_dma40: Get LCPA SRAM from SRAM node")
Signed-off-by: Vinod Koul <vkoul@kernel.org>
---
drivers/dma/ste_dma40.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/dma/ste_dma40.c b/drivers/dma/ste_dma40.c
index c30d00a78eed..56c839241a53 100644
--- a/drivers/dma/ste_dma40.c
+++ b/drivers/dma/ste_dma40.c
@@ -3542,8 +3542,8 @@ static int __init d40_probe(struct platform_device *pdev)
}
base->lcpa_size = resource_size(&res_lcpa);
base->phy_lcpa = res_lcpa.start;
- dev_info(dev, "found LCPA SRAM at 0x%08x, size 0x%08x\n",
- (u32)base->phy_lcpa, base->lcpa_size);
+ dev_info(dev, "found LCPA SRAM at 0x%08x, size %pR\n",
+ (u32)base->phy_lcpa, &base->lcpa_size);
/* We make use of ESRAM memory for this. */
val = readl(base->virtbase + D40_DREG_LCPA);
--
2.40.1
next reply other threads:[~2023-05-17 6:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 6:44 Vinod Koul [this message]
2023-05-17 6:44 ` [PATCH 2/2] dmaengine: ste_dma40: fix typo in enum documentation Vinod Koul
2023-05-17 6:51 ` Linus Walleij
2023-05-17 6:50 ` [PATCH 1/2] dmaengine: ste_dma40: use correct print specfier for resource_size_t Linus Walleij
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=20230517064434.141091-1-vkoul@kernel.org \
--to=vkoul@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lkp@intel.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