The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Ziran Zhang <zhangcoder@yeah.net>
To: markus.elfring@web.de
Cc: airlied@gmail.com, alexander.deucher@amd.com,
	amd-gfx@lists.freedesktop.org, christian.koenig@amd.com,
	dri-devel@lists.freedesktop.org, harry.wentland@amd.com,
	linux-kernel@vger.kernel.org, simona@ffwll.ch,
	siqueira@igalia.com, sunpeng.li@amd.com, zhangcoder@yeah.net
Subject: Re: [PATCH] drm/amd/display: Remove redundant NULL check before kfree() in mod_power_create()
Date: Sat, 27 Jun 2026 21:07:03 +0800	[thread overview]
Message-ID: <20260627130712.4339-1-zhangcoder@yeah.net> (raw)
In-Reply-To: <0d82b2ff-5451-4ba5-9a02-fec93b93484f@web.de>

On Sat, 27 Jun 2026 13:53:13 +0200, Markus Elfring wrote:
> > kfree() safely handles NULL pointers, so there is no need to check for
> > NULL before calling kfree().
> …

> How do you think about to append parentheses to another function name
> in the summary phrase?

> Regards,
> Markus

Oops!  I will send a v3.
Thanks for the review!

Regards,
Ziran Zhang


  reply	other threads:[~2026-06-27 13:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-27  9:26 [PATCH] drm/amd/display: Remove redundant NULL check before kfree in mod_power_create() Ziran Zhang
2026-06-27  9:43 ` [PATCH] drm/amd/display: Remove redundant NULL check before kfree() " Markus Elfring
2026-06-27  9:54   ` Ziran Zhang
2026-06-27 10:09 ` [PATCH v2] drm/amd/display: Remove redundant NULL check before kfree " Ziran Zhang
2026-06-27 11:53   ` Markus Elfring
2026-06-27 13:07     ` Ziran Zhang [this message]
2026-06-27 13:13   ` [PATCH v3] drm/amd/display: Remove redundant NULL check before kfree() " Ziran Zhang

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=20260627130712.4339-1-zhangcoder@yeah.net \
    --to=zhangcoder@yeah.net \
    --cc=airlied@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=harry.wentland@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus.elfring@web.de \
    --cc=simona@ffwll.ch \
    --cc=siqueira@igalia.com \
    --cc=sunpeng.li@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