Media Galleries: Move gallery name generation back to StorageMonitor.

chrome/browser/extensions/api/media_galleries_private/media_galleries_eject_apitest.cc

Index: chrome/browser/extensions/api/media_galleries_private/media_galleries_eject_apitest.cc
===================================================================
--- chrome/browser/extensions/api/media_galleries_private/media_galleries_eject_apitest.cc	(revision 213035)
+++ chrome/browser/extensions/api/media_galleries_private/media_galleries_eject_apitest.cc	(working copy)
@@ -89,8 +89,9 @@
 
   void Attach() {
     DCHECK(chrome::StorageMonitor::GetInstance()->IsInitialized());
-    chrome::StorageInfo info(device_id_, ASCIIToUTF16(kDeviceName), kDevicePath,
-                             string16(), string16(), string16(), 0);
+    chrome::StorageInfo info(device_id_, kDevicePath,
+                             base::ASCIIToUTF16(kDeviceName), base::string16(),

[vandebo (ex-Chrome), 2013/07/23 23:28:55]

Is this to make the devices distinguishable or something?

[Lei Zhang, 2013/07/24 05:13:34]

Yes, for removable devices, the storage label field has similar effects as the
name field did previously. If we never put in |kDeviceName| somewhere, how can
we test for it later in JS?

+                             base::string16(), 0);
     chrome::StorageMonitor::GetInstance()->receiver()->ProcessAttach(info);
     content::RunAllPendingInMessageLoop();
   }