[OE-core] Spurious warning with nested meta layers?

[Andre McCurdy]

Is it valid to nest a meta layer within another meta layer?

After applying the patch below (to create s test layer within the OE
core top-level meta directory) and updating bblayers.conf BBLAYERS
to include openembedded-core/meta/meta-foo, everything seems to work
OK (ie the foo recipe is parsed and usable) however I see a spurious
warning that no .bb files were found within meta-foo:

  WARNING: No bb files matched BBFILE_PATTERN_foo '^/home/andre/rdk/rdk-master/openembedded-core/meta/meta-foo/'

The warning goes away if meta-foo is not nested within another meta
layer.

---
 meta/meta-foo/conf/layer.conf               | 7 +++++++
 meta/meta-foo/recipes-foo/foo/files/foo.txt | 0
 meta/meta-foo/recipes-foo/foo/foo_0.1.bb    | 3 +++
 3 files changed, 10 insertions(+)
 create mode 100644 meta/meta-foo/conf/layer.conf
 create mode 100644 meta/meta-foo/recipes-foo/foo/files/foo.txt
 create mode 100644 meta/meta-foo/recipes-foo/foo/foo_0.1.bb

diff --git a/meta/meta-foo/conf/layer.conf b/meta/meta-foo/conf/layer.conf
new file mode 100644
index 0000000..ef23fc2
--- /dev/null
+++ b/meta/meta-foo/conf/layer.conf
@@ -0,0 +1,7 @@
+BBPATH .= ":${LAYERDIR}"
+
+BBFILES += "${LAYERDIR}/recipes-*/*/*.bb"
+
+BBFILE_COLLECTIONS += "foo"
+BBFILE_PATTERN_foo := "^${LAYERDIR}/"
+BBFILE_PRIORITY_foo = "1"
diff --git a/meta/meta-foo/recipes-foo/foo/files/foo.txt b/meta/meta-foo/recipes-foo/foo/files/foo.txt
new file mode 100644
index 0000000..e69de29
diff --git a/meta/meta-foo/recipes-foo/foo/foo_0.1.bb b/meta/meta-foo/recipes-foo/foo/foo_0.1.bb
new file mode 100644
index 0000000..a5b5412
--- /dev/null
+++ b/meta/meta-foo/recipes-foo/foo/foo_0.1.bb
@@ -0,0 +1,3 @@
+LICENSE = "CLOSED"
+
+SRC_URI = "file://foo.txt"
-- 
1.9.1