From: Ingo Molnar <mingo@kernel.org>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: Borislav Petkov <bp@alien8.de>,
LKML <linux-kernel@vger.kernel.org>, Borislav Petkov <bp@suse.de>,
Jiri Olsa <jolsa@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Robert Richter <rric@kernel.org>
Subject: Re: [PATCH] perf: Move fs.* to generic lib/lk/
Date: Fri, 22 Nov 2013 16:43:29 +0100 [thread overview]
Message-ID: <20131122154317.GB15636@gmail.com> (raw)
In-Reply-To: <20131122145756.GB11305@ghostprotocols.net>
* Arnaldo Carvalho de Melo <acme@ghostprotocols.net> wrote:
> Lets experiment at having things at the right granularity, even if
> it involves many, directly linked, like libperf.a, libraries, one at
> a time, starting with fskapi (or whatever name ends up being
> preferred for this initial one).
That's fine with me - what I stood up against was the idea to merge
into a single place things like the Git helpers, cmdline/option
parser, etc.
The naming problem is mostly non-existent if the concepts are kept
nicely separate: the best name for the debugfs bits is probably
tools/lib/debugfs/, the best name for command line option parser is
tools/lib/cmdline/, the best name for trace event parsing is
tools/lib/traceevents/ [hey, we already have that one in the right
place! ;-)], etc.
Thanks,
Ingo
prev parent reply other threads:[~2013-11-22 15:43 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 21:56 [PATCH] perf: Move fs.* to generic lib/lk/ Borislav Petkov
2013-11-21 7:34 ` Ingo Molnar
2013-11-21 10:07 ` Borislav Petkov
2013-11-21 11:17 ` Ingo Molnar
2013-11-21 11:30 ` Borislav Petkov
2013-11-21 11:42 ` Ingo Molnar
2013-11-21 12:06 ` Borislav Petkov
2013-11-21 12:39 ` Steven Rostedt
2013-11-21 13:49 ` Borislav Petkov
2013-11-21 13:56 ` Steven Rostedt
2013-11-21 14:18 ` Borislav Petkov
2013-11-21 15:12 ` Arnaldo Carvalho de Melo
2013-11-21 15:05 ` Arnaldo Carvalho de Melo
2013-11-21 15:28 ` Borislav Petkov
2013-11-21 17:37 ` Arnaldo Carvalho de Melo
2013-11-21 19:00 ` Borislav Petkov
2013-11-22 12:27 ` Ingo Molnar
2013-11-22 13:50 ` Borislav Petkov
2013-11-22 15:00 ` Arnaldo Carvalho de Melo
2013-11-22 15:20 ` David Ahern
2013-11-22 15:39 ` Ingo Molnar
2013-11-22 15:54 ` Ingo Molnar
2013-11-23 13:12 ` Borislav Petkov
2013-11-26 18:03 ` Ingo Molnar
2013-11-27 15:42 ` Borislav Petkov
2013-11-23 13:04 ` Borislav Petkov
2013-11-26 18:17 ` Ingo Molnar
2013-11-27 15:39 ` Borislav Petkov
2013-11-28 12:16 ` Borislav Petkov
2013-12-02 20:30 ` Arnaldo Carvalho de Melo
2013-11-22 14:57 ` Arnaldo Carvalho de Melo
2013-11-22 15:43 ` Ingo Molnar [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=20131122154317.GB15636@gmail.com \
--to=mingo@kernel.org \
--cc=acme@ghostprotocols.net \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rric@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