All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: "Khatri, Sunil" <Sunil.Khatri@amd.com>,
	"Deucher, Alexander" <Alexander.Deucher@amd.com>,
	"Koenig, Christian" <Christian.Koenig@amd.com>
Cc: "amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/amdgpu: Validate return value of pm_runtime_get_sync
Date: Tue, 4 Mar 2025 12:05:34 -0600	[thread overview]
Message-ID: <88360484-cc77-4837-bf9b-fea050f1b929@amd.com> (raw)
In-Reply-To: <BL1PR12MB57530EA7AEF0BE777E39B93793C82@BL1PR12MB5753.namprd12.prod.outlook.com>

On 3/4/2025 12:03, Khatri, Sunil wrote:
> For new code can you please use drm_err() instead of DRM_ERROR()?
> I see drm_err is not used anywhere in amdgpu driver but display is using it. I think it would be better if I take it in a different patch to change instead. Does that sounds ok ?
> 

DRM_ERROR() doesn't give any information on a multi-GPU system which GPU 
had the problem.  drm_err() does.  So it's the preferred macro for errors.

Up to Alex and Christian if they take this as is or spin it, but I think 
it's a very simple change.

> Regards
> Sunil Khatri
> 
>> +             pm_runtime_put_autosuspend(adev_to_drm(adev)->dev);
>>                goto free_mqd;
>> +     }
>>
>>        r = mqd_hw_default->init_mqd(adev, (void *)queue->mqd.cpu_ptr, userq_props);
>>        if (r) {
> 


  reply	other threads:[~2025-03-04 18:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-04 17:51 [PATCH] drm/amdgpu: Validate return value of pm_runtime_get_sync Sunil Khatri
2025-03-04 17:57 ` Mario Limonciello
2025-03-04 18:03   ` Khatri, Sunil
2025-03-04 18:05     ` Mario Limonciello [this message]
2025-03-04 18:25       ` Alex Deucher

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=88360484-cc77-4837-bf9b-fea050f1b929@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=Christian.Koenig@amd.com \
    --cc=Sunil.Khatri@amd.com \
    --cc=amd-gfx@lists.freedesktop.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 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.