phosphor-mapper: Drop blacklist feature

An interface and path blacklisting feature was implemented in the
python mapper but it isn't used, and it wasn't implemented in the
c++ mapper.  Drop support to make a small improvement to
comprehensional complexity and ease the transition to the c++ mapper.

(From meta-phosphor rev: 6b10fd583d7c1baed14f6076322548f4f097d9db)

Change-Id: I3346f1929689b75553b8331a6ac1b5df0d5c87cb
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>

1 files changed, 0 insertions, 8 deletions

diff --git a/meta-phosphor/recipes-phosphor/dbus/phosphor-mapper-config-native.bb b/meta-phosphor/recipes-phosphor/dbus/phosphor-mapper-config-native.bb
index 976c59b9c..dcc5bd3c1 100644
--- a/meta-phosphor/recipes-phosphor/dbus/phosphor-mapper-config-native.bb
+++ b/meta-phosphor/recipes-phosphor/dbus/phosphor-mapper-config-native.bb
@@ -27,15 +27,7 @@ PHOSPHOR_MAPPER_NAMESPACE = ""
 # Add interfaces to be monitored.
 PHOSPHOR_MAPPER_INTERFACE = ""
 
-# Blacklist paths from being monitored.
-PHOSPHOR_MAPPER_NAMESPACE_BLACKLIST = ""
-
-# Blacklist interfaces from being monitored.
-PHOSPHOR_MAPPER_INTERFACE_BLACKLIST = ""
-
 do_install() {
         install -d ${D}/${namespace_dir}
         install -d ${D}/${interface_dir}
-        install -d ${D}/${blacklist_dir}
-        install -d ${D}/${interfaceblacklist_dir}
 }