[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141217140408.GC11607@kernel.org>
Date: Wed, 17 Dec 2014 11:04:08 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Jiri Olsa <jolsa@...hat.com>
Cc: Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org,
Adrian Hunter <adrian.hunter@...el.com>,
Borislav Petkov <bp@...e.de>, David Ahern <dsahern@...il.com>,
Don Zickus <dzickus@...hat.com>,
Frederic Weisbecker <fweisbec@...il.com>,
Mike Galbraith <efault@....de>,
Namhyung Kim <namhyung@...nel.org>,
Paul Mackerras <paulus@...ba.org>,
Peter Zijlstra <peterz@...radead.org>,
Stephane Eranian <eranian@...gle.com>
Subject: Re: [PATCH 10/18] tools lib: Move asm-generic/bitops/find.h code to
tools/include and tools/lib
Em Wed, Dec 17, 2014 at 02:41:16PM +0100, Jiri Olsa escreveu:
> On Tue, Dec 16, 2014 at 01:57:12PM -0300, Arnaldo Carvalho de Melo wrote:
> > +++ b/tools/perf/MANIFEST
> > @@ -4,8 +4,10 @@ tools/lib/traceevent
> > tools/lib/api
> > tools/lib/symbol/kallsyms.c
> > tools/lib/symbol/kallsyms.h
> > +tools/lib/util/find_next_bit.c
> hum, I had the impression that we will move 'generic' things under 'api' to
> be built separatelly.. so whats the current notion? ;-)
> what kind of code belongs to 'lib/api/...' and what to 'lib/...' ?
Well, the reasoning here was that if libkapi is for functions that
provide glue over kernel APIs, which a set of bitmap handling routines
is not, i.e. that is more generic and not strictly related to the
kernel.
- Arnaldo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists