From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Feng Liu <Feng.Liu3@windriver.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.10.y/5.15.y] pmdomain: ti: Add a null pointer check to the omap_prm_domain_init
Date: Wed, 23 Apr 2025 08:17:07 -0400 [thread overview]
Message-ID: <20250423072444-db6b4ce79d040e68@stable.kernel.org> (raw)
In-Reply-To: <20250423010410.2131206-1-Feng.Liu3@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: 5d7f58ee08434a33340f75ac7ac5071eea9673b3
WARNING: Author mismatch between patch and upstream commit:
Backport author: Feng Liu<Feng.Liu3@windriver.com>
Commit author: Kunwu Chan<chentao@kylinos.cn>
Status in newer kernel trees:
6.14.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: ce666cecc09c)
6.1.y | Present (different SHA1: bc08f5ab11b1)
5.15.y | Not found
Note: The patch differs from the upstream commit:
---
1: 5d7f58ee08434 ! 1: cbad465802664 pmdomain: ti: Add a null pointer check to the omap_prm_domain_init
@@ Metadata
## Commit message ##
pmdomain: ti: Add a null pointer check to the omap_prm_domain_init
+ [ Upstream commit 5d7f58ee08434a33340f75ac7ac5071eea9673b3 ]
+
devm_kasprintf() returns a pointer to dynamically allocated memory
which can be NULL upon failure. Ensure the allocation was successful
by checking the pointer validity.
@@ Commit message
Signed-off-by: Kunwu Chan <chentao@kylinos.cn>
Link: https://lore.kernel.org/r/20240118054257.200814-1-chentao@kylinos.cn
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
+ Signed-off-by: Sasha Levin <sashal@kernel.org>
+ [Minor context change fixed]
+ Signed-off-by: Feng Liu <Feng.Liu3@windriver.com>
+ Signed-off-by: He Zhe <Zhe.He@windriver.com>
- ## drivers/pmdomain/ti/omap_prm.c ##
-@@ drivers/pmdomain/ti/omap_prm.c: static int omap_prm_domain_init(struct device *dev, struct omap_prm *prm)
+ ## drivers/soc/ti/omap_prm.c ##
+@@ drivers/soc/ti/omap_prm.c: static int omap_prm_domain_init(struct device *dev, struct omap_prm *prm)
data = prm->data;
name = devm_kasprintf(dev, GFP_KERNEL, "prm_%s",
data->name);
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.10.y | Success | Success |
| stable/linux-5.15.y | Success | Success |
prev parent reply other threads:[~2025-04-23 12:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 1:04 [PATCH 5.10.y/5.15.y] pmdomain: ti: Add a null pointer check to the omap_prm_domain_init Feng Liu
2025-04-23 12:17 ` 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=20250423072444-db6b4ce79d040e68@stable.kernel.org \
--to=sashal@kernel.org \
--cc=Feng.Liu3@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