From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Howard Chu <howardchu95@gmail.com>
Cc: peterz@infradead.org, mingo@redhat.com, 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 v1 1/2] perf trace: Add tests for BTF general augmentation
Date: Tue, 26 Nov 2024 13:41:29 -0300 [thread overview]
Message-ID: <Z0X6OTPsWOHgmvMr@x1> (raw)
In-Reply-To: <CAH0uvojmPp4-0xb6sObr8Tcw=ujysLMBeebpwON0Ygy=LH63Zg@mail.gmail.com>
On Fri, Nov 22, 2024 at 04:58:00PM -0800, Howard Chu wrote:
> For the first patch, there is:
>
>
> Suggested-by: Ian Rogers <irogers@google.com>
b4 somehow didn't like parts of this process:
⬢ [acme@toolbox perf-tools-next]$ b4 am -ctsl --cc-trailers 20241123005512.342079-1-howardchu95@gmail.com
Grabbing thread from lore.kernel.org/all/20241123005512.342079-1-howardchu95@gmail.com/t.mbox.gz
Checking for newer revisions
Grabbing search results from lore.kernel.org
Analyzing 4 messages in the thread
Looking for additional code-review trailers on lore.kernel.org
Checking attestation on all messages, may take a moment...
---
✓ [PATCH v1 1/2] perf trace: Add tests for BTF general augmentation
+ Link: https://lore.kernel.org/r/20241123005512.342079-2-howardchu95@gmail.com
+ Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
✓ [PATCH v1 2/2] perf docs: Add documentation for --force-btf option
+ Link: https://lore.kernel.org/r/20241123005512.342079-3-howardchu95@gmail.com
+ Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
✓ Signed: DKIM/gmail.com
---
Total patches: 2
---
NOTE: some trailers ignored due to from/email mismatches:
! Trailer: Suggested-by: Ian Rogers <irogers@google.com>
Msg From: Howard Chu <howardchu95@gmail.com>
NOTE: Rerun with -S to apply them anyway
---
Cover: ./20241122_howardchu95_perf_trace_add_tests_for_btf_general_augmentation.cover
Link: https://lore.kernel.org/r/20241123005512.342079-1-howardchu95@gmail.com
Base: applies clean to current tree
git checkout -b 20241122_howardchu95_gmail_com HEAD
git am ./20241122_howardchu95_perf_trace_add_tests_for_btf_general_augmentation.mbx
⬢ [acme@toolbox perf-tools-next]$
next prev parent reply other threads:[~2024-11-26 16:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-23 0:55 [PATCH v1 0/2] perf trace: Add tests for BTF general augmentation Howard Chu
2024-11-23 0:55 ` [PATCH v1 1/2] " Howard Chu
2024-11-23 0:58 ` Howard Chu
2024-11-26 16:41 ` Arnaldo Carvalho de Melo [this message]
2024-11-26 16:49 ` Arnaldo Carvalho de Melo
2024-11-26 17:12 ` Arnaldo Carvalho de Melo
2024-11-26 17:45 ` Howard Chu
2024-11-23 0:55 ` [PATCH v1 2/2] perf docs: Add documentation for --force-btf option Howard Chu
2024-11-26 17:14 ` Arnaldo Carvalho de Melo
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=Z0X6OTPsWOHgmvMr@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=mingo@redhat.com \
--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.