From: Namhyung Kim <namhyung@kernel.org>
To: Yang Jihong <yangjihong1@huawei.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
linux-perf-users <linux-perf-users@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] perf kvm/sched: Use strstarts instead of strncmp to match subcommands
Date: Mon, 8 Aug 2022 14:22:22 -0700 [thread overview]
Message-ID: <CAM9d7cj3HcijAz_C1Y-u87H4XXeR4zW2TFQOxhmSjMuTqHQAzA@mail.gmail.com> (raw)
In-Reply-To: <20220808092408.107399-1-yangjihong1@huawei.com>
Hello,
On Mon, Aug 8, 2022 at 2:27 AM Yang Jihong <yangjihong1@huawei.com> wrote:
>
> Yang Jihong (2):
> perf kvm: Fix subcommand matching error
> perf sched latency: Fix subcommand matching error
Acked-by: Namhyung Kim <namhyung@kernel.org>
Thanks,
Namhyung
>
> tools/perf/builtin-kvm.c | 8 ++++----
> tools/perf/builtin-sched.c | 2 +-
> 2 files changed, 5 insertions(+), 5 deletions(-)
>
> --
> 2.30.GIT
>
next prev parent reply other threads:[~2022-08-08 21:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 9:24 [PATCH 0/2] perf kvm/sched: Use strstarts instead of strncmp to match subcommands Yang Jihong
2022-08-08 9:24 ` [PATCH 1/2] perf kvm: Fix subcommand matching error Yang Jihong
2022-08-08 9:24 ` [PATCH 2/2] perf sched latency: " Yang Jihong
2022-08-08 21:22 ` Namhyung Kim [this message]
2022-08-10 13:16 ` [PATCH 0/2] perf kvm/sched: Use strstarts instead of strncmp to match subcommands 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=CAM9d7cj3HcijAz_C1Y-u87H4XXeR4zW2TFQOxhmSjMuTqHQAzA@mail.gmail.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.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=peterz@infradead.org \
--cc=yangjihong1@huawei.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;
as well as URLs for NNTP newsgroup(s).