From: Feng Tang <feng.tang@intel.com>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: acme@infradead.org, linux-kernel@vger.kernel.org,
namhyung.kim@lge.com, namhyung@kernel.org
Subject: Re: [PATCH 2/2] perf report: Fix build with NO_NEWT=1
Date: Tue, 26 Feb 2013 16:48:50 +0800 [thread overview]
Message-ID: <20130226084850.GA18084@feng-snb> (raw)
In-Reply-To: <1361854923-1814-2-git-send-email-michael@ellerman.id.au>
On Tue, Feb 26, 2013 at 04:02:03PM +1100, Michael Ellerman wrote:
> Commit ad0de09 "Enable the runtime switching of perf data file" broke
> the build with NO_NEWT=1:
>
> CC builtin-report.o
> builtin-report.c: In function '__cmd_report':
> builtin-report.c:479:15: error: 'K_SWITCH_INPUT_DATA' undeclared (first use in this function)
> builtin-report.c:479:15: note: each undeclared identifier is reported only once for each function it appears in
> builtin-report.c: In function 'cmd_report':
> builtin-report.c:823:13: error: 'K_SWITCH_INPUT_DATA' undeclared (first use in this function)
> make: *** [builtin-report.o] Error 1
>
> Fix it by adding a dummy definition of K_SWITCH_INPUT_DATA.
>
> Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
> ---
> tools/perf/util/hist.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tools/perf/util/hist.h b/tools/perf/util/hist.h
> index 609a115..226a4ae 100644
> --- a/tools/perf/util/hist.h
> +++ b/tools/perf/util/hist.h
> @@ -210,6 +210,7 @@ static inline int script_browse(const char *script_opt __maybe_unused)
>
> #define K_LEFT -1000
> #define K_RIGHT -2000
> +#define K_SWITCH_INPUT_DATA -3000
Both patches look good to me, thanks for the fix. But can we use
a better value? -1000, -2000 looks a little awkward.
- Feng
next prev parent reply other threads:[~2013-02-26 8:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 5:02 [PATCH 1/2] perf annotate: Fix build with NO_NEWT=1 Michael Ellerman
2013-02-26 5:02 ` [PATCH 2/2] perf report: " Michael Ellerman
2013-02-26 8:48 ` Feng Tang [this message]
2013-02-26 11:46 ` Michael Ellerman
2013-03-18 10:51 ` [tip:perf/urgent] " tip-bot for Michael Ellerman
2013-02-26 9:02 ` [PATCH 1/2] perf annotate: " Namhyung Kim
2013-02-27 1:14 ` li guang
2013-02-27 1:22 ` Michael Ellerman
2013-02-27 1:29 ` li guang
2013-02-27 1:29 ` li guang
2013-02-27 2:31 ` Namhyung Kim
2013-03-18 10:50 ` [tip:perf/urgent] " tip-bot for Michael Ellerman
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=20130226084850.GA18084@feng-snb \
--to=feng.tang@intel.com \
--cc=acme@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@ellerman.id.au \
--cc=namhyung.kim@lge.com \
--cc=namhyung@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox