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.6.y 2/2] usb: typec: fix pm usage counter imbalance in ucsi_ccg_sync_control()
Date: Tue, 15 Apr 2025 17:43:23 -0400 [thread overview]
Message-ID: <20250415131127-81dfbc8b6031488e@stable.kernel.org> (raw)
In-Reply-To: <20250415015659.312040-2-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: b0e525d7a22ea350e75e2aec22e47fcfafa4cacd
WARNING: Author mismatch between patch and upstream commit:
Backport author: bin.lan.cn@windriver.com
Commit author: GONG Ruiqi<gongruiqi1@huawei.com>
Status in newer kernel trees:
6.14.y | Present (exact SHA1)
6.13.y | Present (exact SHA1)
6.12.y | Present (different SHA1: 976544bdb40a)
Note: The patch differs from the upstream commit:
---
1: b0e525d7a22ea < -: ------------- usb: typec: fix pm usage counter imbalance in ucsi_ccg_sync_control()
-: ------------- > 1: 4cf6fea3b1723 usb: typec: fix pm usage counter imbalance in ucsi_ccg_sync_control()
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.12.y | Success | Success |
next prev parent reply other threads:[~2025-04-15 21:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 1:56 [PATCH 6.6.y 1/2] usb: typec: fix potential array underflow in ucsi_ccg_sync_control() bin.lan.cn
2025-04-15 1:56 ` [PATCH 6.6.y 2/2] usb: typec: fix pm usage counter imbalance " bin.lan.cn
2025-04-15 21:43 ` Sasha Levin [this message]
2025-04-15 21:43 ` [PATCH 6.6.y 1/2] usb: typec: fix potential array underflow " Sasha Levin
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=20250415131127-81dfbc8b6031488e@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 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.