From: John Garry <john.garry@huawei.com>
To: <peterz@infradead.org>, <acme@kernel.org>, <mark.rutland@arm.com>,
<alexander.shishkin@linux.intel.com>, <jolsa@redhat.com>,
<namhyung@kernel.org>, <mingo@redhat.com>
Cc: <irogers@google.com>, <linux-perf-users@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <kjain@linux.ibm.com>,
John Garry <john.garry@huawei.com>
Subject: [PATCH 0/2] perf jevents: Enable build warnings
Date: Sat, 16 Oct 2021 00:48:25 +0800 [thread overview]
Message-ID: <1634316507-227751-1-git-send-email-john.garry@huawei.com> (raw)
Currently jevents builds without any complier warning flags enabled. So
use newly-defined HOSTCFLAGS, which comes from EXTRA_WARNINGS. I am not
100% confident that this is the best way, but sending out for review.
Baseline is be8ecc57f180 (HEAD, acme/perf/core) perf srcline: Use
long-running addr2line per DSO
Thanks!
John Garry (2):
perf jevents: Fix some would-be warnings
perf jevents: Enable warnings through HOSTCFLAGS
tools/perf/Makefile.config | 1 +
tools/perf/Makefile.perf | 2 +-
tools/perf/pmu-events/Build | 2 +-
tools/perf/pmu-events/jevents.c | 10 ++++------
4 files changed, 7 insertions(+), 8 deletions(-)
--
2.26.2
next reply other threads:[~2021-10-15 16:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 16:48 John Garry [this message]
2021-10-15 16:48 ` [PATCH 1/2] perf jevents: Fix some would-be warnings John Garry
2021-10-15 16:48 ` [PATCH 2/2] perf jevents: Enable warnings through HOSTCFLAGS John Garry
2021-10-18 10:41 ` James Clark
2021-10-19 8:37 ` John Garry
2021-10-20 14:31 ` [PATCH 0/2] perf jevents: Enable build warnings Arnaldo Carvalho de Melo
2021-10-20 14:41 ` John Garry
2021-10-20 16:34 ` Arnaldo Carvalho de Melo
2021-10-20 17:25 ` Arnaldo Carvalho de Melo
2021-10-21 20:31 ` [RFC] Support Intel-PT code build in 32-bit arches Arnaldo Carvalho de Melo
2021-10-22 12:23 ` Adrian Hunter
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=1634316507-227751-1-git-send-email-john.garry@huawei.com \
--to=john.garry@huawei.com \
--cc=acme@kernel.org \
--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=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.