From: Yang Jihong <yangjihong1@huawei.com>
To: <peterz@infradead.org>, <mingo@redhat.com>, <acme@kernel.org>,
<mark.rutland@arm.com>, <alexander.shishkin@linux.intel.com>,
<jolsa@kernel.org>, <namhyung@kernel.org>,
<colin.i.king@gmail.com>, <linux-kernel@vger.kernel.org>,
<linux-perf-users@vger.kernel.org>
Cc: <pc@us.ibm.com>, <yhs@fb.com>, <andrii.nakryiko@gmail.com>,
<songliubraving@fb.com>
Subject: Re: [PATCH v2 0/7] perf kwork: A couple of fixes according to review comments
Date: Sat, 6 Aug 2022 17:37:13 +0800 [thread overview]
Message-ID: <417639ef-5c98-35a6-0ec7-501c1a33475a@huawei.com> (raw)
In-Reply-To: <20220730030335.78203-1-yangjihong1@huawei.com>
Hello,
PING.
Regards,
Jihong
.
On 2022/7/30 11:03, Yang Jihong wrote:
> Some issues are fixed based on the comments of several reviewers:
> 1. Add '--synth task' option for record (note from Namhyung)
> 2. Replace hard-coded initialization of nr_tracepoints with ARRAY_SIZE macro (note from Namhyung)
> 3. Fix spelling mistake: "PRINT_TIME_UNIT_MESC_WIDTH" -> "PRINT_TIME_UNIT_MSEC_WIDTH" (note from Namhyung)
> 4. Fix spelling mistake: "Captuer" -> "Capture" (note from Colin)
> 5. Add some {} for multiline for/if blocks (note from Arnaldo)
>
> Modifying based on the latest commit (9a0b36266f7a) at acme/perf/core:
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git perf/core
>
> Yang Jihong (7):
> perf kwork: Add '--synth task' option for record
> perf kwork: Replace hard-coded initialization of nr_tracepoints with
> ARRAY_SIZE macro
> perf kwork: Fix spelling mistake: "Captuer" -> "Capture"
> perf kwork: Fix spelling mistake: "PRINT_TIME_UNIT_MESC_WIDTH" ->
> "PRINT_TIME_UNIT_MSEC_WIDTH"
> perf kwork: Strdup function name in workqueue_work_init
> perf kwork: Expand capacity of bpf entries
> perf kwork: Add some {} for multiline for/if blocks
>
> tools/perf/builtin-kwork.c | 67 +++++++++++++---------
> tools/perf/util/bpf_skel/kwork_trace.bpf.c | 2 +-
> 2 files changed, 40 insertions(+), 29 deletions(-)
>
prev parent reply other threads:[~2022-08-06 9:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-30 3:03 Yang Jihong
2022-07-30 3:03 ` [PATCH v2 1/7] perf kwork: Add '--synth task' option for record Yang Jihong
2022-07-30 3:03 ` [PATCH v2 2/7] perf kwork: Replace hard-coded initialization of nr_tracepoints with ARRAY_SIZE macro Yang Jihong
2022-07-30 3:03 ` [PATCH v2 3/7] perf kwork: Fix spelling mistake: "Captuer" -> "Capture" Yang Jihong
2022-07-30 3:03 ` [PATCH v2 4/7] perf kwork: Fix spelling mistake: "PRINT_TIME_UNIT_MESC_WIDTH" -> "PRINT_TIME_UNIT_MSEC_WIDTH" Yang Jihong
2022-07-30 3:03 ` [PATCH v2 5/7] perf kwork: Strdup function name in workqueue_work_init Yang Jihong
2022-07-30 3:03 ` [PATCH v2 6/7] perf kwork: Expand capacity of bpf entries Yang Jihong
2022-07-30 3:03 ` [PATCH v2 7/7] perf kwork: Add some {} for multiline for/if blocks Yang Jihong
2022-08-06 9:37 ` Yang Jihong [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=417639ef-5c98-35a6-0ec7-501c1a33475a@huawei.com \
--to=yangjihong1@huawei.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=andrii.nakryiko@gmail.com \
--cc=colin.i.king@gmail.com \
--cc=jolsa@kernel.org \
--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=pc@us.ibm.com \
--cc=peterz@infradead.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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®