From: Andi Kleen <ak@linux.intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [PATCH] Fix page-flags build
Date: Thu, 12 Mar 2015 16:16:55 -0700 [thread overview]
Message-ID: <20150312231655.GJ31334@tassilo.jf.intel.com> (raw)
In-Reply-To: <20150312155439.eaaacb7d6bf72d06c7deefff@linux-foundation.org>
> A bit more info would have helped!
It didn't build because libabikfs doesn't exist anymore. Nothing more to say.
> This appears to be a fix for 285a8f247b08c2 ("tools lib api: Rename
> libapikfs.a to libapi.a"), authored by Jiri, committed by Arnaldo and
> presently in linux-next.
Ok. Should get into master then.
-Andi
next prev parent reply other threads:[~2015-03-12 23:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 22:39 [PATCH] Fix page-flags build Andi Kleen
2015-03-12 22:54 ` Andrew Morton
2015-03-12 23:16 ` Andi Kleen [this message]
2015-03-13 10:09 ` Jiri Olsa
2015-05-13 6:24 ` [tip:perf/urgent] tools: Fix tools/vm build tip-bot for Andi Kleen
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=20150312231655.GJ31334@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).