From: Pekka Enberg <penberg@kernel.org>
To: Namhyung Kim <namhyung.kim@lge.com>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>,
Namhyung Kim <namhyung@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/7] perf tools: Move UI bits to tools/perf/ui directory
Date: Mon, 2 Apr 2012 20:43:00 +0300 (EEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1204022042530.1950@tux.localdomain> (raw)
In-Reply-To: <1333003004-6391-2-git-send-email-namhyung.kim@lge.com>
On Thu, 29 Mar 2012, Namhyung Kim wrote:
> Move those files to new directory in order to be prepared to
> further UI work. Makefile and header file pathes are adjusted
> accordingly.
>
> Suggested-by: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
> Signed-off-by: Namhyung Kim <namhyung.kim@lge.com>
Acked-by: Pekka Enberg <penberg@kernel.org>
next prev parent reply other threads:[~2012-04-02 17:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 6:36 [RFC v2 0/7] perf ui: Small preparation for furthure UI work Namhyung Kim
2012-03-29 6:36 ` [PATCH 1/7] perf tools: Move UI bits to tools/perf/ui directory Namhyung Kim
2012-04-02 17:43 ` Pekka Enberg [this message]
2012-03-29 6:36 ` [PATCH 2/7] perf tools: Move GTK+ bits to tools/perf/ui/gtk directory Namhyung Kim
2012-04-02 17:41 ` Pekka Enberg
2012-04-04 18:29 ` [PATCH RESEND 2/2] " Namhyung Kim
2012-03-29 6:36 ` [PATCH 3/7] perf ui: Make setup_browser() generic Namhyung Kim
2012-03-29 6:36 ` [PATCH 4/7] perf ui: Drop arg[cv] arguments from perf_gtk_setup_browser() Namhyung Kim
2012-03-29 6:36 ` [PATCH 5/7] perf ui/gtk: Rename functions for consistency Namhyung Kim
2012-03-29 6:36 ` [PATCH 6/7] perf ui: Add gtk2 support into setup_browser() Namhyung Kim
2012-03-29 6:36 ` [PATCH 7/7] perf ui: Change fallback policy of setup_browser() Namhyung Kim
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=alpine.LFD.2.02.1204022042530.1950@tux.localdomain \
--to=penberg@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=namhyung.kim@lge.com \
--cc=namhyung@gmail.com \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).