Fix unreachable code bug caused by anding with zero, per finnur@.

chrome/browser/enumerate_modules_model_win.cc

Index: chrome/browser/enumerate_modules_model_win.cc
diff --git a/chrome/browser/enumerate_modules_model_win.cc b/chrome/browser/enumerate_modules_model_win.cc
index 563f46453e732c69ef0ecb1d072d9eaddbeb3ce5..29524a7a06bfe145313689a36dfcf90023ab58c9 100644
--- a/chrome/browser/enumerate_modules_model_win.cc
+++ b/chrome/browser/enumerate_modules_model_win.cc
@@ -895,7 +895,7 @@ base::ListValue* EnumerateModulesModel::GetModuleList() const {
               IDS_CONFLICTS_CHECK_POSSIBLE_ACTION_SEPARATOR) +
           base::ASCIIToWide(" ");
 
-      if (module->recommended_action & ModuleEnumerator::NONE) {
+      if (module->recommended_action == ModuleEnumerator::NONE) {

[Finnur, 2014/11/04 17:10:15]

No, you were right. Now that I'm a little fresher in the morning and not as
jet-lagged I realize I gave you the wrong advice. Revert this change and swap
NONE for INVESTIGATING.

         actions = l10n_util::GetStringUTF16(
             IDS_CONFLICTS_CHECK_INVESTIGATING);
       }