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.4.y] drm/i915: Fix memory leak by correcting cache object name in error handler
Date: Tue, 17 Dec 2024 20:23:27 -0500 [thread overview]
Message-ID: <20241217201222-6ed3b88d01db7f28@stable.kernel.org> (raw)
In-Reply-To: <20241217210051.36137-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: b91167d74a0d)
6.6.y | Present (different SHA1: 5cc1c29d5d4e)
6.1.y | Present (different SHA1: 386978fcf9c9)
5.15.y | Present (different SHA1: 5ff57824c3d2)
5.10.y | Present (different SHA1: 4e02296a6d82)
5.4.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: 54eb00b9f2f8 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.4.y | Success | Success |
prev parent reply other threads:[~2024-12-18 1:23 UTC|newest]
Thread overview: 3+ 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.4-stable tree gregkh
2024-12-17 21:00 ` [PATCH 5.4.y] drm/i915: Fix memory leak by correcting cache object name in error handler Jiasheng Jiang
2024-12-18 1:23 ` 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=20241217201222-6ed3b88d01db7f28@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox