From: "Das, Nirmoy" <nirmoy.das@amd.com>
To: "Christian König" <christian.koenig@amd.com>,
amd-gfx@lists.freedesktop.org
Cc: "Sharma, Shashank" <shashank.sharma@amd.com>
Subject: Re: [PATCH 1/2] drm/amdgpu: use IS_ERR for debugfs APIs
Date: Fri, 3 Sep 2021 10:13:38 +0200 [thread overview]
Message-ID: <1fdd6081-b332-fdff-2190-5f8ead784b59@amd.com> (raw)
In-Reply-To: <5aeadf99-0864-1e45-63fa-a9f299d373f7@amd.com>
Hi Christian and Shashank,
Please review the v2 : https://patchwork.freedesktop.org/patch/452175/
In v2, I am returning "PTR_ERR(ent)" instead of -EIO which I think makes more sense.
Regards,
Nirmoy
On 9/3/2021 9:53 AM, Christian König wrote:
> Am 02.09.21 um 13:44 schrieb Nirmoy Das:
>> debugfs APIs returns encoded error so use
>> IS_ERR for checking return value.
>>
>> References: https://gitlab.freedesktop.org/drm/amd/-/issues/1686
>> Signed-off-by: Nirmoy Das <nirmoy.das@amd.com>
>
> Reviewed-by: Christian König <christian.koenig@amd.com>
>
>> ---
>> drivers/gpu/drm/amd/amdgpu/amdgpu_debugfs.c | 6 ++----
>> drivers/gpu/drm/amd/amdgpu/amdgpu_ring.c | 2 +-
>> 2 files changed, 3 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_debugfs.c
>> b/drivers/gpu/drm/amd/amdgpu/amdgpu_debugfs.c
>> index d256215ab2c7..077f9baf74fe 100644
>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_debugfs.c
>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_debugfs.c
>> @@ -1696,18 +1696,16 @@ int amdgpu_debugfs_init(struct amdgpu_device
>> *adev)
>> struct dentry *ent;
>> int r, i;
>> -
>> -
>> ent = debugfs_create_file("amdgpu_preempt_ib", 0600, root, adev,
>> &fops_ib_preempt);
>> - if (!ent) {
>> + if (IS_ERR(ent)) {
>> DRM_ERROR("unable to create amdgpu_preempt_ib debugsfs
>> file\n");
>> return -EIO;
>> }
>> ent = debugfs_create_file("amdgpu_force_sclk", 0200, root, adev,
>> &fops_sclk_set);
>> - if (!ent) {
>> + if (IS_ERR(ent)) {
>> DRM_ERROR("unable to create amdgpu_set_sclk debugsfs file\n");
>> return -EIO;
>> }
>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_ring.c
>> b/drivers/gpu/drm/amd/amdgpu/amdgpu_ring.c
>> index 7b634a1517f9..f40753e1a60d 100644
>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_ring.c
>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_ring.c
>> @@ -428,7 +428,7 @@ int amdgpu_debugfs_ring_init(struct amdgpu_device
>> *adev,
>> ent = debugfs_create_file(name,
>> S_IFREG | S_IRUGO, root,
>> ring, &amdgpu_debugfs_ring_fops);
>> - if (!ent)
>> + if (IS_ERR(ent))
>> return -ENOMEM;
>> i_size_write(ent->d_inode, ring->ring_size + 12);
>
next prev parent reply other threads:[~2021-09-03 8:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 11:44 [PATCH 1/2] drm/amdgpu: use IS_ERR for debugfs APIs Nirmoy Das
2021-09-02 11:44 ` [PATCH 2/2] drm/amdgpu: cleanup debugfs for amdgpu rings Nirmoy Das
2021-09-03 6:36 ` Sharma, Shashank
2021-09-03 8:09 ` Das, Nirmoy
2021-09-03 15:26 ` Sharma, Shashank
2021-09-03 15:51 ` Das, Nirmoy
2021-09-03 16:14 ` Das, Nirmoy
2021-09-05 8:03 ` Sharma, Shashank
2021-09-05 11:31 ` Das, Nirmoy
2021-09-06 16:45 ` Sharma, Shashank
2021-09-08 8:54 ` Das, Nirmoy
2021-09-02 15:23 ` [PATCH 1/2] drm/amdgpu: use IS_ERR for debugfs APIs Sharma, Shashank
2021-09-03 7:53 ` Christian König
2021-09-03 8:13 ` Das, Nirmoy [this message]
2021-09-03 8:17 ` Christian König
2021-09-03 15:28 ` Sharma, Shashank
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=1fdd6081-b332-fdff-2190-5f8ead784b59@amd.com \
--to=nirmoy.das@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=shashank.sharma@amd.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