From: Tom Zanussi <tom.zanu...@linux.intel.com>

The contents of perf.inc are really specific to perf features and
shouldn't use the generic perf.inc name, which implies common recipe
code.  It's always confusing to open up this file and find out that's
not what it is.

Signed-off-by: Tom Zanussi <tom.zanu...@linux.intel.com>
---
 meta/recipes-kernel/perf/{perf.inc => perf-features.inc} | 0
 meta/recipes-kernel/perf/perf_3.4.bb                     | 2 +-
 2 files changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-kernel/perf/{perf.inc => perf-features.inc} (100%)

diff --git a/meta/recipes-kernel/perf/perf.inc 
b/meta/recipes-kernel/perf/perf-features.inc
similarity index 100%
rename from meta/recipes-kernel/perf/perf.inc
rename to meta/recipes-kernel/perf/perf-features.inc
diff --git a/meta/recipes-kernel/perf/perf_3.4.bb 
b/meta/recipes-kernel/perf/perf_3.4.bb
index 22feb46..3c49922 100644
--- a/meta/recipes-kernel/perf/perf_3.4.bb
+++ b/meta/recipes-kernel/perf/perf_3.4.bb
@@ -11,7 +11,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
 
 PR = "r8"
 
-require perf.inc
+require perf-features.inc
 
 BUILDPERF_libc-uclibc = "no"
 
-- 
1.7.11.4


_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Reply via email to