From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Tanmay Shah <tanmay.shah@amd.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH v2] mailbox: zynqmp: setup IPI for each valid child node
Date: Mon, 16 Dec 2024 19:42:17 -0500 [thread overview]
Message-ID: <20241216192841-922fe76161366e54@stable.kernel.org> (raw)
In-Reply-To: <20241216214257.3924162-1-tanmay.shah@amd.com>
[ Sasha's backport helper bot ]
Hi,
Found matching upstream commit: 98fc87fe2937db5a4948c553f69b5a3cc94c230a
Status in newer kernel trees:
6.12.y | Not found
Note: The patch differs from the upstream commit:
---
1: 98fc87fe2937 ! 1: 7d2de1d13592 mailbox: zynqmp: setup IPI for each valid child node
@@ Commit message
Fix this crash by registering IPI setup function for each available child
node.
+ Cc: stable@vger.kernel.org
+ Fixes: 41bcf30100c5 (mailbox: zynqmp: Move buffered IPI setup)
Signed-off-by: Tanmay Shah <tanmay.shah@amd.com>
- Signed-off-by: Jassi Brar <jassisinghbrar@gmail.com>
+ Reviewed-by: Michal Simek <michal.simek@amd.com>
## drivers/mailbox/zynqmp-ipi-mailbox.c ##
@@ drivers/mailbox/zynqmp-ipi-mailbox.c: static int zynqmp_ipi_probe(struct platform_device *pdev)
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.12.y | Success | Success |
| stable/linux-6.6.y | Failed | N/A |
| stable/linux-6.1.y | Failed | N/A |
| stable/linux-5.15.y | Failed | N/A |
| stable/linux-5.10.y | Failed | N/A |
| stable/linux-5.4.y | Failed | N/A |
next prev parent reply other threads:[~2024-12-17 0:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 21:42 [PATCH v2] mailbox: zynqmp: setup IPI for each valid child node Tanmay Shah
2024-12-17 0:42 ` Sasha Levin [this message]
2024-12-18 21:59 ` Sasha Levin
2024-12-19 0:26 ` Tanmay Shah
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=20241216192841-922fe76161366e54@stable.kernel.org \
--to=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tanmay.shah@amd.com \
/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.