Coalesce event router Init calls into their constructors.

chrome/browser/extensions/api/push_messaging/push_messaging_api.cc

Index: chrome/browser/extensions/api/push_messaging/push_messaging_api.cc
diff --git a/chrome/browser/extensions/api/push_messaging/push_messaging_api.cc b/chrome/browser/extensions/api/push_messaging/push_messaging_api.cc
index 3b73fa284ce7ad04a244e90d69e7c7979120a24a..d92305af16281e95976783f8079680ab16237206 100644
--- a/chrome/browser/extensions/api/push_messaging/push_messaging_api.cc
+++ b/chrome/browser/extensions/api/push_messaging/push_messaging_api.cc
@@ -46,11 +46,6 @@ namespace glue = api::push_messaging;
 
 PushMessagingEventRouter::PushMessagingEventRouter(Profile* profile)
     : profile_(profile) {
-}
-
-PushMessagingEventRouter::~PushMessagingEventRouter() {}
-
-void PushMessagingEventRouter::Init() {
   ProfileSyncService* pss = ProfileSyncServiceFactory::GetForProfile(profile_);
   // This may be NULL; for example, for the ChromeOS guest user. In these cases,
   // just return without setting up anything, since it won't work anyway.
@@ -78,6 +73,8 @@ void PushMessagingEventRouter::Init() {
                  content::Source<Profile>(profile_->GetOriginalProfile()));
 }
 
+PushMessagingEventRouter::~PushMessagingEventRouter() {}
+
 void PushMessagingEventRouter::Shutdown() {
   // We need an explicit Shutdown() due to the dependencies among the various
   // ProfileKeyedServices. ProfileSyncService depends on ExtensionSystem, so