chrome: Use base::MessageLoop. (Part 3)

chrome/browser/policy/policy_service_impl.cc

Index: chrome/browser/policy/policy_service_impl.cc
diff --git a/chrome/browser/policy/policy_service_impl.cc b/chrome/browser/policy/policy_service_impl.cc
index 1f126e804aab8dc415b544b88bd6f80a47cb529a..b20ab386a4a457c27e46cace7f5f9a5868998e9d 100644
--- a/chrome/browser/policy/policy_service_impl.cc
+++ b/chrome/browser/policy/policy_service_impl.cc
@@ -120,7 +120,7 @@ void PolicyServiceImpl::NotifyNamespaceUpdated(
     const PolicyMap& current) {
   // If running a unit test that hasn't setup a MessageLoop, don't send any
   // notifications.
-  if (!MessageLoop::current())
+  if (!base::MessageLoop::current())
     return;
 
   // Don't queue up a task if we have no observers - that way Observers added
@@ -132,7 +132,7 @@ void PolicyServiceImpl::NotifyNamespaceUpdated(
   // call to MergeAndTriggerUpdates() by modifying policy.
   scoped_ptr<PolicyChangeInfo> changes(
       new PolicyChangeInfo(ns, previous, current));
-  MessageLoop::current()->PostTask(
+  base::MessageLoop::current()->PostTask(
       FROM_HERE,
       base::Bind(&PolicyServiceImpl::NotifyNamespaceUpdatedTask,
                  weak_ptr_factory_.GetWeakPtr(),