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>,
mark.rutland@arm.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, bwicaksono@nvidia.com,
ilkka@os.amperecomputing.com, suzuki.poulose@arm.com
Subject: Re: [PATCH v2 0/4] perf/arm_cspmu: Fixes and cleanups
Date: Fri, 9 Jun 2023 12:16:47 +0100 [thread overview]
Message-ID: <168630640845.3062687.2554490206521840847.b4-ty@kernel.org> (raw)
In-Reply-To: <cover.1685983270.git.robin.murphy@arm.com>
On Mon, 5 Jun 2023 18:01:30 +0100, Robin Murphy wrote:
> v1: https://lore.kernel.org/linux-arm-kernel/cover.1685619571.git.robin.murphy@arm.com/
>
> Quick update fixing the issues in patch #4 pointed out by Ilkka.
>
> Thanks,
> Robin.
>
> [...]
Applied to will (for-next/perf), thanks!
[1/4] perf/arm_cspmu: Fix event attribute type
https://git.kernel.org/will/c/71e0cb32d5fc
[2/4] ACPI/APMT: Don't register invalid resource
https://git.kernel.org/will/c/87b3b6d53efc
[3/4] perf/arm_cspmu: Clean up ACPI dependency
https://git.kernel.org/will/c/f9bd34e3753e
[4/4] perf/arm_cspmu: Decouple APMT dependency
https://git.kernel.org/will/c/d2e3bb512818
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2023-06-09 11:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 17:01 Robin Murphy
2023-06-05 17:01 ` [PATCH v2 1/4] perf/arm_cspmu: Fix event attribute type Robin Murphy
2023-06-05 17:01 ` [PATCH v2 2/4] ACPI/APMT: Don't register invalid resource Robin Murphy
2023-06-07 14:21 ` Lorenzo Pieralisi
2023-06-05 17:01 ` [PATCH v2 3/4] perf/arm_cspmu: Clean up ACPI dependency Robin Murphy
2023-07-03 9:21 ` Geert Uytterhoeven
2023-07-03 10:56 ` Robin Murphy
2023-06-05 17:01 ` [PATCH v2 4/4] perf/arm_cspmu: Decouple APMT dependency Robin Murphy
2023-06-05 20:29 ` Ilkka Koskinen
2023-06-09 11:16 ` 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=168630640845.3062687.2554490206521840847.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=bwicaksono@nvidia.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 \
--cc=suzuki.poulose@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®