From: Mario Limonciello <mario.limonciello@amd.com>
To: WenTao Liang <vulab@iscas.ac.cn>, Greg KH <gregkh@linuxfoundation.org>
Cc: "Harry Wentland" <harry.wentland@amd.com>,
"Leo Li" <sunpeng.li@amd.com>,
"Rodrigo Siqueira" <siqueira@igalia.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Alex Hung" <alex.hung@amd.com>,
"Aurabindo Pillai" <aurabindo.pillai@amd.com>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] drm/amd/display: set new_stream to NULL after release
Date: Sun, 28 Jun 2026 14:12:47 -0500 [thread overview]
Message-ID: <396b26b4-50ea-4635-9f18-4401778d20a8@amd.com> (raw)
In-Reply-To: <E91B74F1-B7B5-4EF6-A697-634178A2F3A7@iscas.ac.cn>
On 6/28/26 02:49, WenTao Liang wrote:
>
>
>> 2026年6月28日 15:33，Greg KH <gregkh@linuxfoundation.org> 写道：
>>
>> Did you forget to include an Assisted-by: tag?
>
> You're right, the Fixes hash correction in v2 was suggested by the
> reviewer in v1. I'll add a Suggested-by tag in v3. Thanks for pointing
> this out!
I believe Greg is hypothesizing that this mistaken tag was caused by a
tool/model and you didn't mention the tool that you used.
https://docs.kernel.org/process/coding-assistants.html#attribution
prev parent reply other threads:[~2026-06-28 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-28 7:27 [PATCH v2] drm/amd/display: set new_stream to NULL after release WenTao Liang
2026-06-28 7:33 ` Greg KH
2026-06-28 7:49 ` WenTao Liang
2026-06-28 19:12 ` Mario Limonciello [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=396b26b4-50ea-4635-9f18-4401778d20a8@amd.com \
--to=mario.limonciello@amd.com \
--cc=airlied@gmail.com \
--cc=alex.hung@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=aurabindo.pillai@amd.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=harry.wentland@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=siqueira@igalia.com \
--cc=stable@vger.kernel.org \
--cc=sunpeng.li@amd.com \
--cc=vulab@iscas.ac.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.