From: John Garry <john.garry@huawei.com>
To: Kajol Jain <kjain@linux.ibm.com>, <acme@kernel.org>
Cc: <peterz@infradead.org>, <mingo@redhat.com>,
<mark.rutland@arm.com>, <alexander.shishkin@linux.intel.com>,
<pc@us.ibm.com>, <jolsa@redhat.com>, <namhyung@kernel.org>,
<ak@linux.intel.com>, <yao.jin@linux.intel.com>,
<linux-kernel@vger.kernel.org>,
<linux-perf-users@vger.kernel.org>, <irogers@google.com>,
<maddy@linux.ibm.com>, <ravi.bangoria@linux.ibm.com>
Subject: Re: [PATCH v7 1/5] perf/jevents: Remove jevents.h file
Date: Wed, 2 Sep 2020 18:00:47 +0100 [thread overview]
Message-ID: <d2394fae-a124-7988-acd0-99bd42595074@huawei.com> (raw)
In-Reply-To: <20200902160439.335232-2-kjain@linux.ibm.com>
On 02/09/2020 17:04, Kajol Jain wrote:
> This patch removes jevents.h file.
>
> Signed-off-by: Kajol Jain <kjain@linux.ibm.com>
Reviewed-by: John Garry <john.garry@huawei.com>
next prev parent reply other threads:[~2020-09-02 17:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 16:04 [PATCH v7 0/5] powerpc/perf: Add json file support for hv_24x7 core level events Kajol Jain
2020-09-02 16:04 ` [PATCH v7 1/5] perf/jevents: Remove jevents.h file Kajol Jain
2020-09-02 17:00 ` John Garry [this message]
2020-09-02 16:04 ` [PATCH v7 2/5] perf/jevents: Add new structure to pass json fields Kajol Jain
2020-09-02 17:05 ` John Garry
2020-09-04 8:29 ` kajoljain
2020-09-03 14:54 ` Namhyung Kim
2020-09-04 8:30 ` kajoljain
2020-09-02 16:04 ` [PATCH v7 3/5] perf jevents: Add support for parsing perchip/percore events Kajol Jain
2020-09-02 16:04 ` [PATCH v7 4/5] perf/tools: Pass pmu_event structure as a parameter for arch_get_runtimeparam Kajol Jain
2020-09-02 16:04 ` [PATCH v7 5/5] perf/tools/pmu_events/powerpc: Add hv_24x7 core level metric events Kajol Jain
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=d2394fae-a124-7988-acd0-99bd42595074@huawei.com \
--to=john.garry@huawei.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=kjain@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=maddy@linux.ibm.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=pc@us.ibm.com \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@linux.ibm.com \
--cc=yao.jin@linux.intel.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®