From: Markus Elfring <Markus.Elfring@web.de>
To: Charles Han <hanchunchao@inspur.com>,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org
Cc: LKML <linux-kernel@vger.kernel.org>,
David Airlie <airlied@gmail.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Michal Simek <michal.simek@amd.com>,
Simona Vetter <simona@ffwll.ch>,
Thomas Zimmermann <tzimmermann@suse.de>,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Vishal Sagar <vishal.sagar@amd.com>
Subject: Re: [v2] drm: xlnx: zynqmp_dpsub: Add NULL checks in zynqmp_audio_init()
Date: Tue, 11 Feb 2025 08:55:46 +0100 [thread overview]
Message-ID: <03681acf-9524-4fd1-b40d-a7cafe1c5572@web.de> (raw)
In-Reply-To: <20250211032830.2400-1-hanchunchao@inspur.com>
…
> Add NULL check in zynqmp_audio_init(), to handle kernel NULL
> pointer dereference error.
* Can it be more desirable to prevent such issues?
* Would the message subject have been nicer with a key word like “PATCH”
(besides other refinements)?
…
> ---
> drivers/gpu/drm/xlnx/zynqmp_dp_audio.c | 4 ++++
…
Will you become more familiar with patch version descriptions?
https://lore.kernel.org/all/?q=%22This+looks+like+a+new+version+of+a+previously+submitted+patch%22
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.14-rc2#n310
Regards,
Markus
next prev parent reply other threads:[~2025-02-11 7:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 3:28 [v2] drm: xlnx: zynqmp_dpsub: Add NULL check in zynqmp_audio_init Charles Han
2025-02-11 7:55 ` Markus Elfring [this message]
2025-02-11 8:13 ` 答复: [v2] drm: xlnx: zynqmp_dpsub: Add NULL checks in zynqmp_audio_init() Charles Han(韩春超)
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=03681acf-9524-4fd1-b40d-a7cafe1c5572@web.de \
--to=markus.elfring@web.de \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hanchunchao@inspur.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=michal.simek@amd.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=tzimmermann@suse.de \
--cc=vishal.sagar@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
all inboxes | Powered by JetHome®