mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: linux-perf-users@vger.kernel.org, irogers@google.com,
	cyy@cyyself.name,  James Clark <james.clark@linaro.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	 Arnaldo Carvalho de Melo <acme@kernel.org>,
	 Mark Rutland <mark.rutland@arm.com>,
	 Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	 Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	 "Liang, Kan" <kan.liang@linux.intel.com>,
	 Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	 Yoshihiro Furudera <fj5100bi@fujitsu.com>,
	 Weilin Wang <weilin.wang@intel.com>,
	Junhao He <hejunhao3@huawei.com>,
	 Jean-Philippe Romain <jean-philippe.romain@foss.st.com>,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] perf pmu: Dynamically allocate tool PMU
Date: Thu, 27 Feb 2025 08:50:27 -0800	[thread overview]
Message-ID: <174067502701.1401960.11028274407047299720.b4-ty@kernel.org> (raw)
In-Reply-To: <20250226104111.564443-1-james.clark@linaro.org>

On Wed, 26 Feb 2025 10:40:59 +0000, James Clark wrote:
> A few minor fixes that I came across when poking around with the Perf
> list behavior on hybrid Arm.
> 
> Changes since v1:
>   * Rename perf_pmus__new_tool_pmu() -> tool_pmu__new()
> 
> James Clark (3):
>   perf pmu: Dynamically allocate tool PMU
>   perf pmu: Don't double count common sysfs and json events
>   perf list: Document -v option deduplication feature
> 
> [...]
Applied to perf-tools-next, thanks!

Best regards,
Namhyung



      parent reply	other threads:[~2025-02-27 16:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-26 10:40 James Clark
2025-02-26 10:41 ` [PATCH v2 1/3] " James Clark
2025-02-26 10:41 ` [PATCH v2 2/3] perf pmu: Don't double count common sysfs and json events James Clark
2025-02-26 10:41 ` [PATCH v2 3/3] perf list: Document -v option deduplication feature James Clark
2025-02-27 16:50 ` 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=174067502701.1401960.11028274407047299720.b4-ty@kernel.org \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=cyy@cyyself.name \
    --cc=fj5100bi@fujitsu.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hejunhao3@huawei.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jean-philippe.romain@foss.st.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=weilin.wang@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

all inboxes | Powered by JetHome®