From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Jiasheng Jiang <jiashengjiangcool@gmail.com>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.10.y] drm/i915: Fix memory leak by correcting cache object name in error handler
Date: Mon, 16 Dec 2024 19:42:15 -0500 [thread overview]
Message-ID: <20241216193233-9161e6336005fb92@stable.kernel.org> (raw)
In-Reply-To: <20241216161840.4815-1-jiashengjiangcool@gmail.com>
[ Sasha's backport helper bot ]
Hi,
Found matching upstream commit: 2828e5808bcd5aae7fdcd169cac1efa2701fa2dd
WARNING: Author mismatch between patch and found commit:
Backport author: Jiasheng Jiang <jiashengjiangcool@gmail.com>
Commit author: Jiasheng Jiang <jiashengjiangcool@outlook.com>
Status in newer kernel trees:
6.12.y | Present (different SHA1: 1c7f63e645a9)
6.6.y | Present (different SHA1: c98cff29e48f)
6.1.y | Present (different SHA1: 237fe21e40c7)
5.15.y | Present (different SHA1: a4d0c3c28c3b)
5.10.y | Not found
Note: The patch differs from the upstream commit:
---
1: 2828e5808bcd < -: ------------ drm/i915: Fix memory leak by correcting cache object name in error handler
-: ------------ > 1: e0b528005793 drm/i915: Fix memory leak by correcting cache object name in error handler
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.10.y | Success | Success |
next prev parent reply other threads:[~2024-12-17 0:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-15 8:33 FAILED: patch "[PATCH] drm/i915: Fix memory leak by correcting cache object name in" failed to apply to 5.10-stable tree gregkh
2024-12-16 13:29 ` Andi Shyti
[not found] ` <BYAPR05MB6406014F80159A032E3D7A74AD3B2@BYAPR05MB6406.namprd05.prod.outlook.com>
2024-12-17 17:58 ` Andi Shyti
2024-12-16 16:18 ` [PATCH 5.10.y] drm/i915: Fix memory leak by correcting cache object name in error handler Jiasheng Jiang
2024-12-17 0:42 ` Sasha Levin [this message]
2024-12-17 6:42 ` Greg KH
2024-12-17 9:01 ` Greg KH
2024-12-17 20:40 ` Jiasheng Jiang
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=20241216193233-9161e6336005fb92@stable.kernel.org \
--to=sashal@kernel.org \
--cc=jiashengjiangcool@gmail.com \
--cc=stable@vger.kernel.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 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.