From: Markus Elfring <Markus.Elfring@web.de>
To: Dan Carpenter <error27@gmail.com>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Harry Wentland <harry.wentland@amd.com>
Cc: kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Chenyu Chen" <chen-yu.chen@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"David Airlie" <airlied@gmail.com>, "Leo Li" <sunpeng.li@amd.com>,
"Ray Wu" <ray.wu@amd.com>, "Simona Vetter" <simona@ffwll.ch>,
"Rodrigo Siqueira" <siqueira@igalia.com>,
"Ziran Zhang" <zhangcoder@yeah.net>
Subject: Re: [PATCH] drm/amd/display: Clean up allocation in initialize_backlight_caps()
Date: Sun, 28 Jun 2026 16:07:09 +0200 [thread overview]
Message-ID: <8457d83d-436a-431b-9674-749dcf01a860@web.de> (raw)
In-Reply-To: <aenFoICS1syeOPEm@stanley.mountain>
> Just a small cleanup:
> 1) Remove unnecessary initialization.
> 2) Use the new kzalloc_obj() macro.
> 3) Reformat the NULL check to make checkpatch happy.
> 4) Remove the unnecessary NULL check before kfree() since the pointer
> is not NULL and anyway kfree() accepts NULL pointers.
Do these source code adjustments represent a patch squashing approach?
How good does it fit to known development requirements?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v7.1#n81
Regards,
Markus
prev parent reply other threads:[~2026-06-28 14:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 7:09 Dan Carpenter
2026-06-28 14:07 ` Markus Elfring [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=8457d83d-436a-431b-9674-749dcf01a860@web.de \
--to=markus.elfring@web.de \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=chen-yu.chen@amd.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=error27@gmail.com \
--cc=harry.wentland@amd.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ray.wu@amd.com \
--cc=simona@ffwll.ch \
--cc=siqueira@igalia.com \
--cc=sunpeng.li@amd.com \
--cc=zhangcoder@yeah.net \
/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
Powered by JetHome