From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: YueHaibing <yuehaibing@huawei.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Ian Rogers <irogers@google.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] perf metric: Remove duplicate include
Date: Wed, 16 Sep 2020 10:49:02 -0300 [thread overview]
Message-ID: <20200916134902.GN720847@kernel.org> (raw)
In-Reply-To: <CAM9d7cjzPHR4wB3KA_3MfyhwH+PAwF5ucjwWe=xeSL7SHPch+A@mail.gmail.com>
Em Tue, Sep 15, 2020 at 11:51:22PM +0900, Namhyung Kim escreveu:
> Hello,
>
> On Tue, Sep 15, 2020 at 5:16 PM YueHaibing <yuehaibing@huawei.com> wrote:
> >
> > Remove duplicate header which is included twice.
> >
> > Signed-off-by: YueHaibing <yuehaibing@huawei.com>
>
> Acked-by: Namhyung Kim <namhyung@kernel.org>
Thanks, applied.
- Arnaldo
> Thanks
> Namhyung
>
>
> > ---
> > tools/perf/tests/parse-metric.c | 2 --
> > 1 file changed, 2 deletions(-)
> >
> > diff --git a/tools/perf/tests/parse-metric.c b/tools/perf/tests/parse-metric.c
> > index 23db8acc492d..b344decfb91b 100644
> > --- a/tools/perf/tests/parse-metric.c
> > +++ b/tools/perf/tests/parse-metric.c
> > @@ -11,8 +11,6 @@
> > #include "debug.h"
> > #include "expr.h"
> > #include "stat.h"
> > -#include <perf/cpumap.h>
> > -#include <perf/evlist.h>
> >
> > static struct pmu_event pme_test[] = {
> > {
> > --
> > 2.17.1
> >
> >
--
- Arnaldo
prev parent reply other threads:[~2020-09-16 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 8:15 [PATCH -next] perf metric: Remove duplicate include YueHaibing
2020-09-15 14:51 ` Namhyung Kim
2020-09-16 13:49 ` Arnaldo Carvalho de Melo [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=20200916134902.GN720847@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=yuehaibing@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