From: Felix Kuehling <felix.kuehling@amd.com>
To: "Lu Hongfei" <luhongfei@vivo.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Pan, Xinhui" <Xinhui.Pan@amd.com>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"open list:AMD KFD" <amd-gfx@lists.freedesktop.org>,
"open list:DRM DRIVERS" <dri-devel@lists.freedesktop.org>,
"open list" <linux-kernel@vger.kernel.org>,
"Kim, Jonathan" <Jonathan.Kim@amd.com>
Cc: opensource.kernel@vivo.com
Subject: Re: [PATCH v2] gpu: drm/amd: Remove the redundant null pointer check in list_for_each_entry() loops
Date: Mon, 12 Jun 2023 11:25:20 -0400 [thread overview]
Message-ID: <19a8be24-0b5c-4232-d3ba-dc7f269bafd3@amd.com> (raw)
In-Reply-To: <20230612115848.8739-1-luhongfei@vivo.com>
[+Jon]
Am 2023-06-12 um 07:58 schrieb Lu Hongfei:
> pqn bound in list_for_each_entry loop will not be null, so there is
> no need to check whether pqn is NULL or not.
> Thus remove a redundant null pointer check.
>
> Signed-off-by: Lu Hongfei <luhongfei@vivo.com>
> ---
> The filename of the previous version was:
> 0001-gpu-drm-amd-Fix-the-bug-in-list_for_each_entry-loops.patch
>
> The modifications made compared to the previous version are as follows:
> 1. Modified the patch title
> 2. "Thus remove a redundant null pointer check." is used instead of
> "We could remove this check."
>
> drivers/gpu/drm/amd/amdkfd/kfd_debug.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_debug.c b/drivers/gpu/drm/amd/amdkfd/kfd_debug.c
> index cd34e7aaead4..10d0cef844f0 100644
> --- a/drivers/gpu/drm/amd/amdkfd/kfd_debug.c
> +++ b/drivers/gpu/drm/amd/amdkfd/kfd_debug.c
> @@ -1097,9 +1097,6 @@ void kfd_dbg_set_enabled_debug_exception_mask(struct kfd_process *target,
>
> pqm = &target->pqm;
> list_for_each_entry(pqn, &pqm->queues, process_queue_list) {
> - if (!pqn)
Right, this check doesn't make a lot of sense. Jon, was this meant to
check pqn->q?
Regards,
Felix
> - continue;
> -
> found_mask |= pqn->q->properties.exception_status;
> }
>
next prev parent reply other threads:[~2023-06-12 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 11:58 [PATCH v2] gpu: drm/amd: Remove the redundant null pointer check in list_for_each_entry() loops Lu Hongfei
2023-06-12 15:25 ` Felix Kuehling [this message]
2023-06-12 15:39 ` Kim, Jonathan
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=19a8be24-0b5c-4232-d3ba-dc7f269bafd3@amd.com \
--to=felix.kuehling@amd.com \
--cc=Jonathan.Kim@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luhongfei@vivo.com \
--cc=opensource.kernel@vivo.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