From: Sasha Levin <sashal@kernel.org>
To: phasta@kernel.org
Cc: gregkh@linuxfoundation.org, christian.koenig@amd.com,
ckoenig.leichtzumerken@gmail.com, dakr@kernel.org,
dan.carpenter@linaro.org, daniel.vetter@ffwll.ch,
dri-devel@lists.freedesktop.org, matthew.brost@intel.com,
robdclark@chromium.org, tvrtko.ursulin@igalia.com,
stable-commits@vger.kernel.org
Subject: Re: Patch "drm/sched: Fix potential double free in drm_sched_job_add_resv_dependencies" has been added to the 6.1-stable tree
Date: Tue, 28 Oct 2025 13:47:00 -0400 [thread overview]
Message-ID: <aQEBlErx17wdKkh1@laps> (raw)
In-Reply-To: <48644db5444c493aa0ec022b9708d3c71cd9f038.camel@mailbox.org>
On Mon, Oct 27, 2025 at 01:05:17PM +0100, Philipp Stanner wrote:
>On Mon, 2025-10-27 at 12:36 +0100, gregkh@linuxfoundation.org wrote:
>> Cc: Christian König <ckoenig.leichtzumerken@gmail.com>
>
>What has happened with the encoding here?
>
>@Christian, your mail was UTF-8, wasn't it?
The end result in both the queue[1] as well as the released kernel[2] looks
correct, so I'll go ahead and blame Greg's mail sending scripts :p
I don't think there's anything that needs to be done here...
[1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/releases/6.17.5/drm-sched-fix-potential-double-free-in-drm_sched_job_add_resv_dependencies.patch
[2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.17.5&id=fdfb47e85af1e11ec822c82739dde2dd8dff5115
--
Thanks,
Sasha
prev parent reply other threads:[~2025-10-28 17:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 8:14 FAILED: patch "[PATCH] drm/sched: Fix potential double free in" failed to apply to 6.1-stable tree gregkh
2025-10-21 13:12 ` [PATCH 6.1.y] drm/sched: Fix potential double free in drm_sched_job_add_resv_dependencies Sasha Levin
2025-10-27 11:36 ` Patch "drm/sched: Fix potential double free in drm_sched_job_add_resv_dependencies" has been added to the 6.1-stable tree gregkh
2025-10-27 12:05 ` Philipp Stanner
2025-10-28 17:47 ` Sasha Levin [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=aQEBlErx17wdKkh1@laps \
--to=sashal@kernel.org \
--cc=christian.koenig@amd.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=dakr@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=matthew.brost@intel.com \
--cc=phasta@kernel.org \
--cc=robdclark@chromium.org \
--cc=stable-commits@vger.kernel.org \
--cc=tvrtko.ursulin@igalia.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 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.