Clean-up refactoring of chrome_content_browser_client to use GetPermissionContext consistently.

chrome/browser/services/gcm/push_messaging_permission_context.cc

Index: chrome/browser/services/gcm/push_messaging_permission_context.cc
diff --git a/chrome/browser/services/gcm/push_messaging_permission_context.cc b/chrome/browser/services/gcm/push_messaging_permission_context.cc
index 0cb23dab9da186fe350965b97e6194d4a79fab53..bb39adce372104e099fdf73788a3e546eb9621db 100644
--- a/chrome/browser/services/gcm/push_messaging_permission_context.cc
+++ b/chrome/browser/services/gcm/push_messaging_permission_context.cc
@@ -63,6 +63,12 @@ ContentSetting PushMessagingPermissionContext::GetPermissionStatus(
 #endif
 }
 
+void PushMessagingPermissionContext::CancelPermissionRequest(
+    content::WebContents* web_contents, const PermissionRequestID& id) {
+  // TODO(peter): consider implementing this method.
+  NOTIMPLEMENTED() << "CancelPermission not implemented for push messaging";
+}
+
 // Unlike other permissions, push is decided by the following algorithm
 //  - You need to request it from a top level domain
 //  - You need to have notification permission granted.