From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: bin.lan.cn@windriver.com, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1.y] drm/mediatek: Fix coverity issue with unintentional integer overflow
Date: Tue, 18 Mar 2025 11:12:59 -0400 [thread overview]
Message-ID: <20250318083858-1b355b0baaaae6d4@stable.kernel.org> (raw)
In-Reply-To: <20250318011519.3924779-1-bin.lan.cn@windriver.com>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: b0b0d811eac6b4c52cb9ad632fa6384cf48869e7
WARNING: Author mismatch between patch and upstream commit:
Backport author: bin.lan.cn@windriver.com
Commit author: Jason-JH.Lin<jason-jh.lin@mediatek.com>
Status in newer kernel trees:
6.13.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: 96312a251d4d)
Note: The patch differs from the upstream commit:
---
1: b0b0d811eac6b < -: ------------- drm/mediatek: Fix coverity issue with unintentional integer overflow
-: ------------- > 1: 81185a14fd7b0 drm/mediatek: Fix coverity issue with unintentional integer overflow
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
prev parent reply other threads:[~2025-03-18 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 1:15 [PATCH 6.1.y] drm/mediatek: Fix coverity issue with unintentional integer overflow bin.lan.cn
2025-03-18 15:12 ` 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=20250318083858-1b355b0baaaae6d4@stable.kernel.org \
--to=sashal@kernel.org \
--cc=bin.lan.cn@windriver.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