Move systemInfo.cpu API out out experimental namespace.

chrome/common/extensions/permissions/api_permission.h

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef CHROME_COMMON_EXTENSIONS_PERMISSIONS_API_PERMISSION_H_
 #define CHROME_COMMON_EXTENSIONS_PERMISSIONS_API_PERMISSION_H_
 
 #include <map>
 #include <set>
 #include <string>
@@ skipping 94 matching lines @@
     kRtcPrivate,
     kScreensaver,
     kSerial,
     kSessionRestore,
     kSocket,
     kStorage,
     kStreamsPrivate,
     kSyncFileSystem,
     kSystemPrivate,
     kSystemIndicator,
     kSystemInfoDisplay,

[Tim Song, 2013/05/29 18:19:24]

There is a kSystemInfoDisplay permission here. Would it be a good idea to merge
them into a single systemInfo permission?

[Hongbo Min, 2013/05/30 11:51:12]

Agree.

[Tim Song, 2013/05/31 01:08:35]

With further thought, we should keep these permissions separate as
systemInfo.display is permitted for the stable channel right now, and we should
just leave systemInfo.cpu in dev.

     kTab,
     kTabCapture,
     kTerminalPrivate,
     kTopSites,
     kTts,
     kTtsEngine,
     kUnlimitedStorage,
     kUsb,
     kUsbDevice,
     kVideoCapture,
     kWallpaperPrivate,
     kWebNavigation,
     kWebRequest,
     kWebRequestBlocking,
     kWebRequestInternal,
     kWebSocketProxyPrivate,
     kWebstorePrivate,
     kWebView,
+    kSystemInfoCpu,
     kEnumBoundary
   };
 
   struct CheckParam {
   };
 
   explicit APIPermission(const APIPermissionInfo* info);
 
   virtual ~APIPermission();
 
@@ skipping 143 matching lines @@
   const char* const name_;
   const int flags_;
   const int l10n_message_id_;
   const PermissionMessage::ID message_id_;
   const APIPermissionConstructor api_permission_constructor_;
 };
 
 }  // namespace extensions
 
 #endif  // CHROME_COMMON_EXTENSIONS_PERMISSIONS_API_PERMISSION_H_