From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Howard Chu <howardchu95@gmail.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@kernel.org, irogers@google.com, adrian.hunter@intel.com,
kan.liang@linux.intel.com, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] perf trace: Add more tests for BTF-augmented perf trace
Date: Thu, 26 Dec 2024 12:17:46 -0300 [thread overview]
Message-ID: <Z21zmkbi87kybE84@x1> (raw)
In-Reply-To: <CAH0uvohvzQi_iE0q3A8jZF4P+cwu=4P1Az2guNKP3ckPon9HxA@mail.gmail.com>
On Mon, Dec 23, 2024 at 06:03:11PM -0800, Howard Chu wrote:
> On Mon, Dec 23, 2024 at 11:40 AM Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> > On Mon, Dec 23, 2024 at 04:02:43PM -0300, Arnaldo Carvalho de Melo wrote:
> > So its not just when running in paralell, anyway, its merged, we can go
> > on from what we got there.
> Thanks, I will resolve this issue and send v5 along with the
> documentation changes you suggested.
I got v4 merged meanwhile, we can go on from there, with further patches
polishihg those aspects.
Thanks,
- Arnaldo
next prev parent reply other threads:[~2024-12-26 15:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-15 19:07 [PATCH v4 0/2] perf trace: Add more tests for BTF-augmented perf trace Howard Chu
2024-12-15 19:07 ` [PATCH v4 1/2] perf trace: Add tests for BTF general augmentation Howard Chu
2024-12-15 19:07 ` [PATCH v4 2/2] perf docs: Add documentation for --force-btf option Howard Chu
2024-12-23 19:06 ` Arnaldo Carvalho de Melo
2024-12-16 19:58 ` [PATCH v4 0/2] perf trace: Add more tests for BTF-augmented perf trace Namhyung Kim
2024-12-23 19:02 ` Arnaldo Carvalho de Melo
2024-12-23 19:40 ` Arnaldo Carvalho de Melo
2024-12-24 2:03 ` Howard Chu
2024-12-26 15:17 ` Arnaldo Carvalho de Melo [this message]
2025-01-11 0:52 ` Howard Chu
2025-01-13 15:57 ` Arnaldo Carvalho de Melo
2025-01-18 18:28 ` Namhyung Kim
2025-01-22 0:19 ` Howard Chu
2025-01-23 23:53 ` Namhyung Kim
2025-02-01 0:14 ` Howard Chu
2025-02-04 3:16 ` Namhyung Kim
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=Z21zmkbi87kybE84@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=howardchu95@gmail.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=mark.rutland@arm.com \
--cc=namhyung@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 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.