From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: Besar Wicaksono <bwicaksono@nvidia.com>,
will@kernel.org, robin.murphy@arm.com,
ilkka@os.amperecomputing.com
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
mark.rutland@arm.com, treding@nvidia.com, jonathanh@nvidia.com,
vsethi@nvidia.com, rwiley@nvidia.com, sdonthineni@nvidia.com
Subject: Re: [PATCH v3 1/5] perf/arm_cspmu: Add arm_cspmu_acpi_dev_get
Date: Tue, 30 Sep 2025 09:38:05 +0100 [thread overview]
Message-ID: <e21159ef-d438-4944-adb3-eb8e7c801d9e@arm.com> (raw)
In-Reply-To: <20250930002604.346306-2-bwicaksono@nvidia.com>
On 30/09/2025 01:26, Besar Wicaksono wrote:
> Add interface to get ACPI device associated with the
> PMU. This ACPI device may contain additional properties
> not covered by the standard properties.
>
> Signed-off-by: Besar Wicaksono <bwicaksono@nvidia.com>
Repeat: Where is the user ?
Suzuki
next prev parent reply other threads:[~2025-09-30 8:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 0:25 [PATCH v3 0/5] perf/arm_cspmu: Preparatory patches for NVIDIA T410 PMU Besar Wicaksono
2025-09-30 0:26 ` [PATCH v3 1/5] perf/arm_cspmu: Add arm_cspmu_acpi_dev_get Besar Wicaksono
2025-09-30 8:38 ` Suzuki K Poulose [this message]
[not found] ` <SJ0PR12MB5676DD9C94CB7155D3897DEBA01AA@SJ0PR12MB5676.namprd12.prod.outlook.com>
2025-09-30 13:05 ` Suzuki K Poulose
2025-09-30 13:14 ` Besar Wicaksono
2025-09-30 0:26 ` [PATCH v3 2/5] perf/arm_cspmu: Add callback to reset filter config Besar Wicaksono
2025-09-30 0:26 ` [PATCH v3 3/5] perf/arm_cspmu: Add pmpidr support Besar Wicaksono
2025-09-30 0:26 ` [PATCH v3 4/5] perf/arm_cspmu: nvidia: Add revision id matching Besar Wicaksono
2025-09-30 0:26 ` [PATCH v3 5/5] perf/arm_cspmu: nvidia: Add pmevfiltr2 support Besar Wicaksono
2025-11-03 14:57 ` [PATCH v3 0/5] perf/arm_cspmu: Preparatory patches for NVIDIA T410 PMU Will Deacon
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=e21159ef-d438-4944-adb3-eb8e7c801d9e@arm.com \
--to=suzuki.poulose@arm.com \
--cc=bwicaksono@nvidia.com \
--cc=ilkka@os.amperecomputing.com \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robin.murphy@arm.com \
--cc=rwiley@nvidia.com \
--cc=sdonthineni@nvidia.com \
--cc=treding@nvidia.com \
--cc=vsethi@nvidia.com \
--cc=will@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
all inboxes | Powered by JetHome®