[PATCH] classes/rm_work: rename RM_WORK_WHITELIST to RM_WORK_EXCLUDE

[PATCH] classes/rm_work: rename RM_WORK_WHITELIST to RM_WORK_EXCLUDE

[Paul Eggleton]

This really functions as a blacklist, not a whitelist, since we are
listing recipes to exclude. To avoid any possibility of confusion, since
this was a recent addition, rename the variable.

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
---
 meta/classes/rm_work.bbclass |   10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/meta/classes/rm_work.bbclass b/meta/classes/rm_work.bbclass
index 54287bf..1642af7 100644
--- a/meta/classes/rm_work.bbclass
+++ b/meta/classes/rm_work.bbclass
@@ -5,10 +5,10 @@
 #
 # INHERIT += "rm_work"
 #
-# To inhibit rm_work for some recipes, specify them in RM_WORK_WHITELIST.
+# To inhibit rm_work for some recipes, specify them in RM_WORK_EXCLUDE.
 # For example, in conf/local.conf:
 #
-# RM_WORK_WHITELIST += "icu-native icu busybox"
+# RM_WORK_EXCLUDE += "icu-native icu busybox"
 #
 
 # Use the completion scheduler by default when rm_work is active
@@ -19,10 +19,10 @@ RMWORK_ORIG_TASK := "${BB_DEFAULT_TASK}"
 BB_DEFAULT_TASK = "rm_work_all"
 
 do_rm_work () {
-    # If the recipe name is in the RM_WORK_WHITELIST, skip the recipe.
-    for p in ${RM_WORK_WHITELIST}; do
+    # If the recipe name is in the RM_WORK_EXCLUDE, skip the recipe.
+    for p in ${RM_WORK_EXCLUDE}; do
         if [ "$p" = "${PN}" ]; then
-            bbnote "rm_work: Skipping ${PN} since it is in RM_WORK_WHITELIST"
+            bbnote "rm_work: Skipping ${PN} since it is in RM_WORK_EXCLUDE"
             exit 0
         fi
     done
-- 
1.7.10.4