From: Borislav Petkov <bp@amd64.org>
To: Arnaldo Carvalho de Melo <acme@infradead.org>
Cc: "fweisbec@gmail.com" <fweisbec@gmail.com>,
"mingo@elte.hu" <mingo@elte.hu>,
"peterz@infradead.org" <peterz@infradead.org>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 7/9] perf: Export cpumap
Date: Fri, 6 Aug 2010 16:49:39 +0200 [thread overview]
Message-ID: <20100806144939.GD21628@aftab> (raw)
In-Reply-To: <20100806143912.GB13780@ghostprotocols.net>
From: Arnaldo Carvalho de Melo <acme@infradead.org>
Date: Fri, Aug 06, 2010 at 10:39:12AM -0400
> Em Fri, Aug 06, 2010 at 04:25:11PM +0200, Borislav Petkov escreveu:
> > From: Borislav Petkov <borislav.petkov@amd.com>
> >
> > Export cpu counting and cpumap manipulating utils for general use. This
> > pulls ctype.c along.
> >
> > Signed-off-by: Borislav Petkov <borislav.petkov@amd.com>
>
> Is this independent of previous patches? I.e. to be applied to current
> perf/core?
I'm afraid not since earlier patches in the series introduce the
toplevel Makefile that glues all the different tools/lib/* parts
together. However, I could extract the toplevel Makefile parts and
cpumap.c and ctype.c if you really need it now - I've been doing this so
often lately that I could do it with my eyes closed now :o).
--
Regards/Gruss,
Boris.
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2010-08-06 14:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 14:25 [RFC PATCH 00/9] RAS daemon prototype, v2 Borislav Petkov
2010-08-06 14:25 ` [RFC PATCH 1/9] x86, mce: Notify about corrected events too Borislav Petkov
2010-08-06 14:25 ` [RFC PATCH 2/9] amd64_edac: Remove polling mechanism Borislav Petkov
2010-08-06 14:25 ` [RFC PATCH 3/9] perf_events: Export an assortment of functions Borislav Petkov
2010-08-06 14:25 ` [RFC PATCH 4/9] mce: Add persistent events Borislav Petkov
2010-08-06 14:57 ` Peter Zijlstra
2010-09-01 0:13 ` Steven Rostedt
2010-09-01 6:14 ` Ingo Molnar
2010-09-01 14:54 ` Steven Rostedt
2010-08-06 14:25 ` [RFC PATCH 5/9] perf: Move trace stuff into tools/lib/trace Borislav Petkov
2010-09-01 0:15 ` Steven Rostedt
2010-09-01 8:10 ` Borislav Petkov
2010-09-01 14:55 ` Steven Rostedt
2010-08-06 14:25 ` [RFC PATCH 6/9] perf: Export debugfs utilities Borislav Petkov
2010-08-06 14:25 ` [RFC PATCH 7/9] perf: Export cpumap Borislav Petkov
2010-08-06 14:39 ` Arnaldo Carvalho de Melo
2010-08-06 14:49 ` Borislav Petkov [this message]
2010-08-06 15:14 ` Arnaldo Carvalho de Melo
2010-08-06 16:04 ` Borislav Petkov
2010-08-06 21:48 ` Arnaldo Carvalho de Melo
2010-08-06 14:25 ` [RFC PATCH 8/9] perf: Carve out mmap helpers for general use Borislav Petkov
2010-08-06 14:25 ` [RFC PATCH 9/9] tools, ras: Add a RAS daemon Borislav Petkov
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=20100806144939.GD21628@aftab \
--to=bp@amd64.org \
--cc=acme@infradead.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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).