From: Will Deacon <will@kernel.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
blakgeof@amazon.com, mark.rutland@arm.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
ilkka@os.amperecomputing.com
Subject: Re: [PATCH 0/3] perf: Arm CMN updates
Date: Fri, 28 Jul 2023 16:40:42 +0100 [thread overview]
Message-ID: <169055106672.1935989.16792278281794617341.b4-ty@kernel.org> (raw)
In-Reply-To: <cover.1688746690.git.robin.murphy@arm.com>
On Fri, 7 Jul 2023 17:38:10 +0100, Robin Murphy wrote:
> Here's another CMN update which unfortunately due to circumstances
> didn't manage to be ready in time for 6.5. I realise it's a bit early
> now, but I'm about to be offline for 4 weeks so hey. For anyone playing
> along at home, the HN-S is not documented not in the CMN-700 TRM, but
> in its own special supplement[1].
>
> Thanks,
> Robin.
>
> [...]
Applied to will (for-next/perf), thanks!
[1/3] perf/arm-cmn: Remove spurious event aliases
https://git.kernel.org/will/c/00df90934c9e
[2/3] perf/arm-cmn: Refactor HN-F event selector macros
https://git.kernel.org/will/c/b1b7dc38e482
[3/3] perf/arm-cmn: Add CMN-700 r3 support
https://git.kernel.org/will/c/ac18ea1a8935
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2023-07-28 15:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 16:38 Robin Murphy
2023-07-07 16:38 ` [PATCH 1/3] perf/arm-cmn: Remove spurious event aliases Robin Murphy
2023-07-07 16:38 ` [PATCH 2/3] perf/arm-cmn: Refactor HN-F event selector macros Robin Murphy
2023-07-07 16:38 ` [PATCH 3/3] perf/arm-cmn: Add CMN-700 r3 support Robin Murphy
2023-07-28 15:40 ` Will Deacon [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=169055106672.1935989.16792278281794617341.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=blakgeof@amazon.com \
--cc=catalin.marinas@arm.com \
--cc=ilkka@os.amperecomputing.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robin.murphy@arm.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
all inboxes | Powered by JetHome®