Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751407AbbEGEvA (ORCPT ); Thu, 7 May 2015 00:51:00 -0400 Received: from TYO202.gate.nec.co.jp ([210.143.35.52]:50082 "EHLO tyo202.gate.nec.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750841AbbEGEu5 convert rfc822-to-8bit (ORCPT ); Thu, 7 May 2015 00:50:57 -0400 From: Naoya Horiguchi To: Jiri Olsa , Arnaldo Carvalho de Melo CC: Sukadev Bhattiprolu , Will Deacon , Peter Zijlstra , Ingo Molnar , "linux-kernel@vger.kernel.org" Subject: [PATCH] tools/vm: fix build failure Thread-Topic: [PATCH] tools/vm: fix build failure Thread-Index: AQHQiID7bx6C3S6riUm2EGz+GuSG9w== Date: Thu, 7 May 2015 04:47:55 +0000 Message-ID: <1430974072-813-1-git-send-email-n-horiguchi@ah.jp.nec.com> Accept-Language: ja-JP, en-US Content-Language: ja-JP X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.128.101.3] Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1000 Lines: 29 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 --- 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/