public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
	Borislav Petkov <bp@alien8.de>
Cc: LKML <linux-kernel@vger.kernel.org>, Borislav Petkov <bp@suse.de>,
	Ingo Molnar <mingo@kernel.org>, Jiri Olsa <jolsa@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Robert Richter <rric@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Namhyung Kim <namhyung@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Stanislav Fomichev <stfomichev@yandex-team.ru>,
	Stephane Eranian <eranian@google.com>,
	Andi Kleen <ak@linux.intel.com>,
	Arjan van de Ven <arjan@linux.intel.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Mike Galbraith <efault@gmx.de>, Pekka Enberg <penberg@kernel.org>,
	Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 0/2] perf tool: Carve out fs.* stuff
Date: Sun, 08 Dec 2013 10:42:48 -0700	[thread overview]
Message-ID: <52A4AF98.8040001@gmail.com> (raw)
In-Reply-To: <20131205174725.GF10333@ghostprotocols.net>

On 12/5/13, 10:47 AM, Arnaldo Carvalho de Melo wrote:
> Sorry, some editing problem happened here... Now with proper subject
> line.
>
> - Arnaldo
>
> Em Thu, Dec 05, 2013 at 05:25:50PM +0100, Borislav Petkov escreveu:
>> From: Borislav Petkov <bp@suse.de>
>>
>> Ok,
>>
>> step one: carve out fs-related stuff into a libapikfs.a library.
>
> Adding some more people to the CC list, but from a quick look, this
> is in line with what we discussed so far, so I'm ok with it.
>
> For those people in the CC list, Acked-by would be really, really
> appreciated.

Something is missing. From tools/perf:

$ make O=/tmp/perf

Assembler messages:
Fatal error: can't create /tmp/perf/fs/fs.o: No such file or directory
make[2]: *** [/tmp/perf/fs/fs.o] Error 1
make[2]: *** Waiting for unfinished jobs....
   CC       /tmp/perf/bench/mem-memcpy.o
Assembler messages:
Fatal error: can't create /tmp/perf/fs/debugfs.o: No such file or directory
make[2]: *** [/tmp/perf/fs/debugfs.o] Error 1
make[1]: *** [/tmp/perf/libapikfs.a] Error 2
make[1]: *** Waiting for unfinished jobs....

David

  reply	other threads:[~2013-12-08 17:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05 16:25 [PATCH 0/2] perf tool: Carve out fs.* stuff Borislav Petkov
2013-12-05 16:25 ` [PATCH 1/2] tools/: Convert to new topic libraries Borislav Petkov
2013-12-09 10:22   ` Jiri Olsa
2013-12-09 10:42     ` Borislav Petkov
2013-12-05 16:25 ` [PATCH 2/2] tools/: Move fs.* to lib/api/fs/ Borislav Petkov
2013-12-09 10:26   ` Jiri Olsa
2013-12-09 10:43     ` Borislav Petkov
2013-12-05 17:47 ` [PATCH 0/2] perf tool: Carve out fs.* stuff Arnaldo Carvalho de Melo
2013-12-08 17:42   ` David Ahern [this message]
2013-12-09 10:39     ` Borislav Petkov
2013-12-09 10:30 ` Jiri Olsa

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=52A4AF98.8040001@gmail.com \
    --to=dsahern@gmail.com \
    --cc=acme@ghostprotocols.net \
    --cc=adrian.hunter@intel.com \
    --cc=ak@linux.intel.com \
    --cc=arjan@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=bp@suse.de \
    --cc=efault@gmx.de \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@gmail.com \
    --cc=paulus@samba.org \
    --cc=penberg@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=rric@kernel.org \
    --cc=stfomichev@yandex-team.ru \
    /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