mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
To: Jiri Olsa <jolsa@redhat.com>, Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>,
	Will Deacon <will.deacon@arm.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@elte.hu>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Andi Kleen <andi@firstfloor.org>
Subject: Re: [PATCH] tools/vm: fix build failure
Date: Thu, 7 May 2015 05:02:03 +0000	[thread overview]
Message-ID: <20150507050202.GD7745@hori1.linux.bs1.fc.nec.co.jp> (raw)
In-Reply-To: <1430974072-813-1-git-send-email-n-horiguchi@ah.jp.nec.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1203 bytes --]

On Thu, May 07, 2015 at 04:47:55AM +0000, Horiguchi Naoya(堀口 直也) wrote:
> libapikfs.a was renamed to libapi.a on commit 285a8f247b08 ("tools lib api:
> Rename libapikfs.a to libapi.a"), but tools/vm/Makefile still refers to the
> old file name, which breaks the build on tools/vm. This patch fixes it.
> 
> Signed-off-by: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>

Ah, this was already posted in https://lkml.org/lkml/2015/3/12/964,
but not merged for some reason.
Could someone pick it, please?

Thanks,
Naoya Horiguchi

> ---
>  tools/vm/Makefile | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git v4.1-rc2.orig/tools/vm/Makefile v4.1-rc2/tools/vm/Makefile
> index ac884b65a072..93aadaf7ff63 100644
> --- v4.1-rc2.orig/tools/vm/Makefile
> +++ v4.1-rc2/tools/vm/Makefile
> @@ -3,7 +3,7 @@
>  TARGETS=page-types slabinfo page_owner_sort
>  
>  LIB_DIR = ../lib/api
> -LIBS = $(LIB_DIR)/libapikfs.a
> +LIBS = $(LIB_DIR)/libapi.a
>  
>  CC = $(CROSS_COMPILE)gcc
>  CFLAGS = -Wall -Wextra -I../lib/
> -- 
> 2.1.0
> ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

  reply	other threads:[~2015-05-07  5:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07  4:47 Naoya Horiguchi
2015-05-07  5:02 ` Naoya Horiguchi [this message]
2015-05-07 15:52   ` Arnaldo Carvalho de Melo

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=20150507050202.GD7745@hori1.linux.bs1.fc.nec.co.jp \
    --to=n-horiguchi@ah.jp.nec.com \
    --cc=acme@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=sukadev@linux.vnet.ibm.com \
    --cc=will.deacon@arm.com \
    /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

all inboxes | Powered by JetHome®