From: Thomas Zimmermann <tzimmermann@suse.de>
To: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH -next] drm: simpledrm: print resource info using '%pr'
Date: Thu, 13 May 2021 15:03:40 +0200 [thread overview]
Message-ID: <7bc970ed-007f-6374-b7f8-71707606a6b9@suse.de> (raw)
In-Reply-To: <20210512233459.19534-1-rdunlap@infradead.org>
[-- Attachment #1.1: Type: text/plain, Size: 2477 bytes --]
Hi
Am 13.05.21 um 01:34 schrieb Randy Dunlap:
> struct resource start and end fields are not always long long,
> so using %llx to print them can cause build warnings (below).
> Fix these by using the special "%pr" for printing struct resource info.
>
> ../drivers/gpu/drm/tiny/simpledrm.c: In function ‘simpledrm_device_init_mm’:
> ../include/drm/drm_print.h:412:32: warning: format ‘%llx’
expects argument of type ‘long long unsigned int’, but argument 3 has type ‘resource_size_t {aka unsigned int}’ [-Wformat=]
> ../drivers/gpu/drm/tiny/simpledrm.c:533:54: note: format string is defined here
> drm_err(dev, "could not acquire memory range [0x%llx:0x%llx]: error
%d\n",
> ~~~^
> %x
> ../include/drm/drm_print.h:412:32: warning: format ‘%llx’
expects argument of type ‘long long unsigned int’, but argument 4 has type ‘resource_size_t {aka unsigned int}’ [-Wformat=]
> ../drivers/gpu/drm/tiny/simpledrm.c:533:61: note: format string is defined here
> drm_err(dev, "could not acquire memory range [0x%llx:0x%llx]: error
%d\n",
> ~~~^
> %x
>
> Fixes: 4aae79f77e3a ("drm/simpledrm: Acquire memory aperture for framebuffer")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Thomas Zimmermann <tzimmermann@suse.de>
> Cc: dri-devel@lists.freedesktop.org
Queued up for drm-misc-next. Thanks a lot.
Best regards
Thomas
> ---
> drivers/gpu/drm/tiny/simpledrm.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> --- linux-next-20210512.orig/drivers/gpu/drm/tiny/simpledrm.c
> +++ linux-next-20210512/drivers/gpu/drm/tiny/simpledrm.c
> @@ -530,8 +530,8 @@ static int simpledrm_device_init_mm(stru
>
> ret = devm_aperture_acquire_from_firmware(dev, mem->start, resource_size(mem));
> if (ret) {
> - drm_err(dev, "could not acquire memory range [0x%llx:0x%llx]: error %d\n",
> - mem->start, mem->end, ret);
> + drm_err(dev, "could not acquire memory range %pr: error %d\n",
> + mem, ret);
> return ret;
> }
>
>
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
prev parent reply other threads:[~2021-05-13 13:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 23:34 Randy Dunlap
2021-05-13 13:03 ` Thomas Zimmermann [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=7bc970ed-007f-6374-b7f8-71707606a6b9@suse.de \
--to=tzimmermann@suse.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
/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®