From: Greg KH <gregkh@linuxfoundation.org>
To: "Christian König" <christian.koenig@amd.com>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
Ramesh.Errabolu@amd.com, Alex Deucher <alexander.deucher@amd.com>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Sumit Semwal <sumit.semwal@linaro.org>
Subject: Re: Patch "drm/amdgpu: Remove amdgpu_device arg from free_sgt api (v2)" has been added to the 5.10-stable tree
Date: Tue, 29 Apr 2025 07:24:44 +0200 [thread overview]
Message-ID: <2025042922-elliptic-impish-9c91@gregkh> (raw)
In-Reply-To: <d5b5c2c8-4c44-4500-a56b-12888abda85b@amd.com>
On Mon, Apr 28, 2025 at 08:20:02PM +0200, Christian König wrote:
> On 4/26/25 15:40, Sasha Levin wrote:
> > This is a note to let you know that I've just added the patch titled
> >
> > drm/amdgpu: Remove amdgpu_device arg from free_sgt api (v2)
> >
> > to the 5.10-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > drm-amdgpu-remove-amdgpu_device-arg-from-free_sgt-ap.patch
> > and it can be found in the queue-5.10 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
>
> Mhm, why has that patch been picked up for backporting? It's a cleanup and not a bug fix.
>
> When some other fix depends on it it's probably ok to backport it as well, but stand alone it would probably rather hurt than help,
That is exactly why it is needed, see below:
> > Stable-dep-of: c0dd8a9253fa ("drm/amdgpu/dma_buf: fix page_link check")
Hope this helps, thanks!
greg k-h
next prev parent reply other threads:[~2025-04-29 5:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250426134009.817330-1-sashal@kernel.org>
2025-04-28 18:20 ` Patch "drm/amdgpu: Remove amdgpu_device arg from free_sgt api (v2)" has been added to the 5.10-stable tree Christian König
2025-04-29 5:24 ` Greg KH [this message]
2025-04-29 7:08 ` Christian König
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=2025042922-elliptic-impish-9c91@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Ramesh.Errabolu@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--cc=simona@ffwll.ch \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
/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