From: "Charles Han(韩春超)" <hanchunchao@inspur.com>
To: "Markus.Elfring@web.de" <Markus.Elfring@web.de>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"airlied@gmail.com" <airlied@gmail.com>,
"laurent.pinchart@ideasonboard.com"
<laurent.pinchart@ideasonboard.com>,
"maarten.lankhorst@linux.intel.com"
<maarten.lankhorst@linux.intel.com>,
"mripard@kernel.org" <mripard@kernel.org>,
"michal.simek@amd.com" <michal.simek@amd.com>,
"simona@ffwll.ch" <simona@ffwll.ch>,
"tzimmermann@suse.de" <tzimmermann@suse.de>,
"tomi.valkeinen@ideasonboard.com"
<tomi.valkeinen@ideasonboard.com>,
"vishal.sagar@amd.com" <vishal.sagar@amd.com>
Subject: 答复: [v2] drm: xlnx: zynqmp_dpsub: Add NULL checks in zynqmp_audio_init()
Date: Tue, 11 Feb 2025 08:13:57 +0000 [thread overview]
Message-ID: <918c999b8e1b45989138bbd33c154b4c@inspur.com> (raw)
In-Reply-To: <03681acf-9524-4fd1-b40d-a7cafe1c5572@web.de>
[-- Attachment #1: Type: text/plain, Size: 1485 bytes --]
Thank you for your suggestions. I will read these documents carefully.
-----邮件原件-----
发件人: Markus Elfring <Markus.Elfring@web.de>
发送时间: 2025年2月11日 15:56
收件人: Charles Han(韩春超) <hanchunchao@inspur.com>; dri-devel@lists.freedesktop.org; linux-arm-kernel@lists.infradead.org
抄送: 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>
主题: Re: [v2] drm: xlnx: zynqmp_dpsub: Add NULL checks in zynqmp_audio_init()
…
> 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
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 3830 bytes --]
prev parent reply other threads:[~2025-02-11 8:15 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 ` [v2] drm: xlnx: zynqmp_dpsub: Add NULL checks in zynqmp_audio_init() Markus Elfring
2025-02-11 8:13 ` Charles Han(韩春超) [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=918c999b8e1b45989138bbd33c154b4c@inspur.com \
--to=hanchunchao@inspur.com \
--cc=Markus.Elfring@web.de \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--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®