Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Andre Przywara <andre.przywara@arm.com>,
	stable@vger.kernel.org, stable-commits@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
	James Morse <james.morse@arm.com>,
	Ben Horgan <ben.horgan@arm.com>,
	Reinette Chatre <reinette.chatre@intel.com>,
	Fenghua Yu <fenghuay@nvidia.com>
Subject: Re: Patch "arm_mpam: let low level MSC accessors return an error" has been added to the 7.3-stable tree
Date: Wed, 18 Nov 2026 07:39:59 -0500	[thread overview]
Message-ID: <20261118124002.3727477-3-sashal@kernel.org> (raw)
In-Reply-To: <8b078536-4101-42d4-bbad-d251cedba4f0@arm.com>

On Wed, Nov 18, 2026 at 11:03:40AM +0100, Andre Przywara wrote:
> I will send the stable backport patch ASAP.

Dropped 84e8795c271a ("arm_mpam: let low level MSC accessors return an error"),
a3a94c13c442 ("arm_mpam: propagate MSC access errors for state saving
function") and 197a7a41e6e0 ("arm_mpam: On saving mbwu state read the monitors
before clearing CFG_MBWU_CTL") from the 7.3 queue. I'll pick up your adapted
7.3 backport of 197a7a41e6e0 once it's posted.

Also dropped 643b64025650 ("arm_mpam: Release the mon_sel lock on
mpam_save_mbwu_state() errors"), which needs the mon_sel_lock guard class that
7.3 does not have.

-- 
Thanks,
Sasha

      reply	other threads:[~2026-11-18 12:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20261117143200.1638480-1-sashal@kernel.org>
2026-11-17 16:47 ` Patch "arm_mpam: let low level MSC accessors return an error" has been added to the 7.3-stable tree Andre Przywara
     [not found]   ` <20261118002307.3zUgWZ-5BRbOHUDq8BVKrBK3MWMNodzJn7ZS05iBHNA@z>
2026-11-18  0:23     ` Sasha Levin
2026-11-18 10:03       ` Andre Przywara
2026-11-18 12:39         ` 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=20261118124002.3727477-3-sashal@kernel.org \
    --to=sashal@kernel.org \
    --cc=andre.przywara@arm.com \
    --cc=ben.horgan@arm.com \
    --cc=fenghuay@nvidia.com \
    --cc=james.morse@arm.com \
    --cc=reinette.chatre@intel.com \
    --cc=stable-commits@vger.kernel.org \
    --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