From: Namhyung Kim <namhyung@kernel.org>
To: liguang <lig.fnst@cn.fujitsu.com>
Cc: a.p.zijlstra@chello.nl, paulus@samba.org, mingo@redhat.com,
acme@ghostprotocols.net, jolsa@redhat.com, penberg@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] perf: correct a build error
Date: Tue, 26 Feb 2013 18:06:24 +0900 [thread overview]
Message-ID: <87txozsaun.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <1361851974-25307-2-git-send-email-lig.fnst@cn.fujitsu.com> (liguang's message of "Tue, 26 Feb 2013 12:12:53 +0800")
Hi liguang,
On Tue, 26 Feb 2013 12:12:53 +0800, liguang wrote:
> builtin-annotate.c: In function 'hists__find_annotations':
> builtin-annotate.c:161:4: error: duplicate case value
> builtin-annotate.c:154:4: error: previously used here
>
> it happened when no newt installed
Thanks for fixing this. Please see my other post on the same problem
reported by Michael Ellerman.
Thanks,
Namhyung
>
> Signed-off-by: liguang <lig.fnst@cn.fujitsu.com>
> ---
> tools/perf/util/hist.h | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tools/perf/util/hist.h b/tools/perf/util/hist.h
> index 3862468..b4436e9 100644
> --- a/tools/perf/util/hist.h
> +++ b/tools/perf/util/hist.h
> @@ -208,8 +208,8 @@ static inline int script_browse(const char *script_opt __maybe_unused)
> return 0;
> }
>
> -#define K_LEFT -1
> -#define K_RIGHT -2
> +#define K_LEFT -2
> +#define K_RIGHT -3
> #endif
>
> #ifdef GTK2_SUPPORT
next prev parent reply other threads:[~2013-02-26 9:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 4:12 [PATCH 1/3] perf: sort command-list.txt by alphabet order liguang
2013-02-26 4:12 ` [PATCH 2/3] perf: correct a build error liguang
2013-02-26 9:06 ` Namhyung Kim [this message]
2013-02-26 4:12 ` [PATCH 3/3] perf: add dwarf regs map for mips liguang
2013-03-01 0:37 ` [PATCH 1/3] perf: sort command-list.txt by alphabet order li guang
2013-03-21 10:52 ` [tip:perf/core] perf tools: Sort command-list.txt alphabetically tip-bot for liguang
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=87txozsaun.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=jolsa@redhat.com \
--cc=lig.fnst@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=penberg@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 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.