Don't use base::MessageLoop::{Quit,QuitClosure} in chrome/

chrome/browser/history/android/sqlite_cursor.h

Index: chrome/browser/history/android/sqlite_cursor.h
diff --git a/chrome/browser/history/android/sqlite_cursor.h b/chrome/browser/history/android/sqlite_cursor.h
index 97f85bd1d7beaf8245486a187b83b9a3e80a2e0f..c828ad2942d2c28cf6d68bea4c5937f9cfda7c01 100644
--- a/chrome/browser/history/android/sqlite_cursor.h
+++ b/chrome/browser/history/android/sqlite_cursor.h
@@ -45,8 +45,8 @@ class SQLiteCursor {
   // give unit tests a chance to run the message loop before event_.Wait is
   // invoked, The OnGetMoveToResult() and OnGetFaviconResult() is used to notify
   // the test observer in the UI thread when the task's result comes back, it
-  // calls MessageLoop::Quit() to exit the loop, then the event.Wait() is
-  // called. Basically, Two threads are used to simulate 3 threads' behavior
+  // calls MessageLoop::QuitWhenIdle() to exit the loop, then the event.Wait()
+  // is called. Basically, Two threads are used to simulate 3 threads' behavior
   // here.
   // The whole observer design is only for test purpose and should only be used
   // in unit test.