All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Ian Rogers <irogers@google.com>,
	James Clark <james.clark@linaro.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-perf-users@vger.kernel.org
Subject: [GIT PULL] perf-tools fixes for v7.3-rc3
Date: Mon,  7 Sep 2026 10:25:57 -0700	[thread overview]
Message-ID: <20260907172557.3679541-1-namhyung@kernel.org> (raw)

Hi Linus,

Please consider pulling the following changes in perf tools for v7.3.

Thanks,
Namhyung


The following changes since commit cee9395acd8043be0644b25c34bfa86623f2b935:

  Linux 7.3-rc1 (2026-08-30 13:34:40 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools.git tags/perf-tools-fixes-for-v7.3-2026-09-07

for you to fetch changes up to aadea57f532882d8bab444646863c7ef8a778ff1:

  perf powerpc-vpadtl: Fix raw_size of DTL samples (2026-08-30 23:11:35 -0700)

----------------------------------------------------------------
perf-tools fixes for v7.3-rc3

Here are two simple fixes for this cycle.

 - Do not use separate debug files for Intel PT decoding.
 - Fix size of raw data in the PowerPC VPA DTL samples.

Signed-off-by: Namhyung Kim <namhyung@kernel.org>

----------------------------------------------------------------
Adrian Hunter (1):
      perf symbol: Do not use debug file as the binary type

Wang Yan (1):
      perf powerpc-vpadtl: Fix raw_size of DTL samples

 tools/perf/util/powerpc-vpadtl.c |  2 +-
 tools/perf/util/symbol.c         | 11 ++++++++++-
 2 files changed, 11 insertions(+), 2 deletions(-)

             reply	other threads:[~2026-09-07 17:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07 17:25 Namhyung Kim [this message]
2026-09-07 17:42 ` [GIT PULL] perf-tools fixes for v7.3-rc3 pr-tracker-bot

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=20260907172557.3679541-1-namhyung@kernel.org \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.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 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.