stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Robin Murphy <robin.murphy@arm.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.10/5.15] perf/arm-cmn: Initialise cmn->cpu earlier
Date: Mon,  2 Jun 2025 12:14:31 -0400	[thread overview]
Message-ID: <20250602093940-487065edd0d224fa@stable.kernel.org> (raw)
In-Reply-To: <32923ed9af28f3857fd64f7cd884895e717258b0.1748861349.git.robin.murphy@arm.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: 597704e201068db3d104de3c7a4d447ff8209127

Status in newer kernel trees:
6.15.y | Present (different SHA1: 7b6afec7588f)
6.14.y | Present (different SHA1: 6a7fed0595c2)
6.12.y | Present (different SHA1: fb3a1c1d24ae)
6.6.y | Present (different SHA1: 711b013373b0)
6.1.y | Present (different SHA1: 57c8a80f0b02)
5.15.y | Not found

Note: The patch differs from the upstream commit:
---
1:  597704e201068 < -:  ------------- perf/arm-cmn: Initialise cmn->cpu earlier
-:  ------------- > 1:  ff356633c92f4 perf/arm-cmn: Initialise cmn->cpu earlier
---

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   |

      reply	other threads:[~2025-06-02 16:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-02 11:27 [PATCH 5.10/5.15] perf/arm-cmn: Initialise cmn->cpu earlier Robin Murphy
2025-06-02 16:14 ` 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=20250602093940-487065edd0d224fa@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=robin.murphy@arm.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;
as well as URLs for NNTP newsgroup(s).