All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Besar Wicaksono <bwicaksono@nvidia.com>
Cc: acme@redhat.com, leo.yan@arm.com, james.clark@arm.com,
	irogers@google.com, mark.rutland@arm.com, jolsa@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-perf-users@vger.kernel.org, linux-tegra@vger.kernel.org,
	vsethi@nvidia.com, rwiley@nvidia.com, skelley@nvidia.com,
	ywan@nvidia.com, treding@nvidia.com, jonathanh@nvidia.com
Subject: Re: [PATCH 0/2] arm64: Support NVIDIA Olympus for Perf Arm SPE
Date: Wed, 24 Dec 2025 11:39:15 -0800	[thread overview]
Message-ID: <aUxBY01uNp8gnEPq@google.com> (raw)
In-Reply-To: <20251219231325.2742580-1-bwicaksono@nvidia.com>

On Fri, Dec 19, 2025 at 11:13:23PM +0000, Besar Wicaksono wrote:
> This series support NVIDIA Olympus CPU in Perf Arm SPE.
> The first patch syncs the kernel header to the tools header.
> The second patch adds NVIDIA Olympus into perf's Neoverse SPE data source list.
> 
> Besar Wicaksono (2):
>   tools headers arm64: Add NVIDIA Olympus part
>   perf arm-spe: Add NVIDIA Olympus to neoverse list

Applied to perf-tools, thanks!

Best regards,
Namhyung



      parent reply	other threads:[~2025-12-24 19:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-19 23:13 [PATCH 0/2] arm64: Support NVIDIA Olympus for Perf Arm SPE Besar Wicaksono
2025-12-19 23:13 ` [PATCH 1/2] tools headers arm64: Add NVIDIA Olympus part Besar Wicaksono
2025-12-19 23:13 ` [PATCH 2/2] perf arm-spe: Add NVIDIA Olympus to neoverse list Besar Wicaksono
2025-12-22  9:22 ` [PATCH 0/2] arm64: Support NVIDIA Olympus for Perf Arm SPE Leo Yan
2025-12-24 19:39 ` Namhyung Kim [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=aUxBY01uNp8gnEPq@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@redhat.com \
    --cc=bwicaksono@nvidia.com \
    --cc=irogers@google.com \
    --cc=james.clark@arm.com \
    --cc=jolsa@kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=leo.yan@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=rwiley@nvidia.com \
    --cc=skelley@nvidia.com \
    --cc=treding@nvidia.com \
    --cc=vsethi@nvidia.com \
    --cc=ywan@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.