All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Ian Rogers <irogers@google.com>,
	Kan Liang <kan.liang@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-perf-users@vger.kernel.org,
	Athira Rajeev <atrajeev@linux.vnet.ibm.com>
Subject: Re: [PATCHSET 0/4] perf annotate-data: Update data-type profiling quality (v2)
Date: Thu, 22 Aug 2024 17:54:17 -0300	[thread overview]
Message-ID: <Zselec3mxmkd723n@x1> (raw)
In-Reply-To: <20240821232628.353177-1-namhyung@kernel.org>

On Wed, Aug 21, 2024 at 04:26:24PM -0700, Namhyung Kim wrote:
> Hello,
> 
> This is continuation of data type profiling series to improve its quality.
> I've also found some more bugs and room for improvements.
> 
> Acutally it depends on the a couple of fixes I sent out yesterday.
> But as they will be merged to perf-tools-next, I omitted them here.

Thanks, applied to perf-tools-next,

- Arnaldo

      parent reply	other threads:[~2024-08-22 20:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-21 23:26 [PATCHSET 0/4] perf annotate-data: Update data-type profiling quality (v2) Namhyung Kim
2024-08-21 23:26 ` [PATCH 1/4] perf dwarf-aux: Handle bitfield members from pointer access Namhyung Kim
2024-08-21 23:26 ` [PATCH 2/4] perf annotate-data: Update debug messages Namhyung Kim
2024-08-21 23:26 ` [PATCH 3/4] perf annotate-data: Update stack slot for the store Namhyung Kim
2024-08-21 23:26 ` [PATCH 4/4] perf annotate-data: Copy back variable types after move Namhyung Kim
2024-08-22 20:54 ` Arnaldo Carvalho de Melo [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=Zselec3mxmkd723n@x1 \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=atrajeev@linux.vnet.ibm.com \
    --cc=irogers@google.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=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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.