From: Yussef Dalton <yussef.dalton@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>, tzimmermann@suse.de
Cc: javierm@redhat.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/tiny: print 'struct resource *' correctly
Date: Sun, 17 Dec 2023 00:12:18 +0100 [thread overview]
Message-ID: <78ec36c9-5e87-4c83-bdbf-5680f6eaff4c@gmail.com> (raw)
In-Reply-To: <35984b5f-d4f5-4d45-9e17-b41140ff78e0@infradead.org>
On 10/15/23 17:35, Randy Dunlap wrote:
>
>
> On 10/15/23 06:11, Yussef Dalton wrote:
>> Since format specifier %pr refers to a 'struct resource *', there is no
>> need to take the address of the 'res' variable since it is already of
>> type 'struct resource *'.
>>
>> Signed-off-by: Yussef Dalton <yussef.dalton@gmail.com>
>
> Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
>
> Thanks.
>
>> ---
>> drivers/gpu/drm/tiny/ofdrm.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/tiny/ofdrm.c b/drivers/gpu/drm/tiny/ofdrm.c
>> index 2d999a0facde..6372ab383747 100644
>> --- a/drivers/gpu/drm/tiny/ofdrm.c
>> +++ b/drivers/gpu/drm/tiny/ofdrm.c
>> @@ -1208,13 +1208,13 @@ static struct ofdrm_device *ofdrm_device_create(struct drm_driver *drv,
>>
>> ret = devm_aperture_acquire_from_firmware(dev, fb_pgbase, fb_pgsize);
>> if (ret) {
>> - drm_err(dev, "could not acquire memory range %pr: error %d\n", &res, ret);
>> + drm_err(dev, "could not acquire memory range %pr: error %d\n", res, ret);
>> return ERR_PTR(ret);
>> }
>>
>> mem = devm_request_mem_region(&pdev->dev, fb_pgbase, fb_pgsize, drv->name);
>> if (!mem) {
>> - drm_warn(dev, "could not acquire memory region %pr\n", &res);
>> + drm_warn(dev, "could not acquire memory region %pr\n", res);
>> return ERR_PTR(-ENOMEM);
>> }
>>
>
Hi,
Sorry for the bump, but is there any news on my patch?
Regards,
Yussef
prev parent reply other threads:[~2023-12-16 23:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-15 13:11 Yussef Dalton
2023-10-15 15:35 ` Randy Dunlap
2023-12-16 23:12 ` Yussef Dalton [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=78ec36c9-5e87-4c83-bdbf-5680f6eaff4c@gmail.com \
--to=yussef.dalton@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=tzimmermann@suse.de \
/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®