From: Will Deacon <will@kernel.org>
To: Ben Horgan <ben.horgan@arm.com>
Cc: "james.morse@arm.com" <james.morse@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Fenghua Yu <fenghuay@nvidia.com>,
Guangshuo Li <lgs201920130244@gmail.com>,
Reinette Chatre <reinette.chatre@intel.com>,
Dave Martin <Dave.Martin@arm.com>,
Andre Przywara <andre.przywara@arm.com>
Subject: Re: [GIT PULL] arm_mpam fixes for v7.2-rc2
Date: Wed, 15 Jul 2026 14:01:05 +0100 [thread overview]
Message-ID: <aleEkbcWsYdZPgtW@willie-the-truck> (raw)
In-Reply-To: <d39e20fe-e4ab-4bbb-8e97-b68400ece11a@arm.com>
Hi Ben,
On Thu, Jul 09, 2026 at 05:23:38PM +0100, Ben Horgan wrote:
> On 7/9/26 16:48, Ben Horgan wrote:
> > I hope this method works for sending you MPAM changes but please let me know if
> > you would like them some other way or I've made a mistake. It's not a signed tag
> > as I still need to sort out my GPG key. The change authored by be me hasn't got
> > an Reviewed-by's or Tested-by's but it's been on the list since the middle of
> > May and James is on leave.
> >
> > Fix the reset values for two MPAM controls that are not known to exist in
> > silicon. Fix a NULL pointer dereference on the driver teardown path.
> >
> Sorry, this is a retake. I forgot to add my Sob on the patches.
>
> The following changes since commit 8cdeaa50eae8dad34885515f62559ee83e7e8dda:
>
> Linux 7.2-rc2 (2026-07-05 14:44:06 -1000)
>
> are available in the Git repository at:
>
> git@git.gitlab.arm.com:linux-arm/linux-bh.git tags/mpam-fixes-7.2-rc2-RETAKE
Thanks, but I'll probably just pick these from the list given that your
key isn't sorted out yet.
In future, it's probably easiest if you go down the route that James
used to tread where you collect the mpam patches up and then send them
out as a series (with your SoB added and with me and Catalin on cc) once
they've been reviewed and you're happy with them. Then we can just grab
'em that way. I think that's probably easiest to start with, but we can
revisit it if the number of patches becomes too much.
Does that sound ok?
Will
next prev parent reply other threads:[~2026-07-15 13:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 15:48 [GIT PULL] arm_mpam fixes for v7.2-rc2 Ben Horgan
2026-07-09 16:23 ` Ben Horgan
2026-07-15 13:01 ` Will Deacon [this message]
2026-07-15 13:10 ` Ben Horgan
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=aleEkbcWsYdZPgtW@willie-the-truck \
--to=will@kernel.org \
--cc=Dave.Martin@arm.com \
--cc=andre.przywara@arm.com \
--cc=ben.horgan@arm.com \
--cc=catalin.marinas@arm.com \
--cc=fenghuay@nvidia.com \
--cc=james.morse@arm.com \
--cc=lgs201920130244@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reinette.chatre@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox