[Cleanup] Remove StringPrintf from global namespace

chrome/browser/password_manager/native_backend_gnome_x.cc

 // 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.
 
 #include "chrome/browser/password_manager/native_backend_gnome_x.h"
 
 #include <dlfcn.h>
 #include <gnome-keyring.h>
 
 #include <map>
@@ skipping 677 matching lines @@
   // Successful read of actual data. Try migration if necessary.
   if (!migrate_tried_)
     MigrateToProfileSpecificLogins();
   return true;
 }
 
 std::string NativeBackendGnome::GetProfileSpecificAppString() const {
   // Originally, the application string was always just "chrome" and used only
   // so that we had *something* to search for since GNOME Keyring won't search
   // for nothing. Now we use it to distinguish passwords for different profiles.
-  return StringPrintf("%s-%d", kGnomeKeyringAppString, profile_id_);
+  return base::StringPrintf("%s-%d", kGnomeKeyringAppString, profile_id_);
 }
 
 void NativeBackendGnome::MigrateToProfileSpecificLogins() {
   DCHECK(BrowserThread::CurrentlyOn(BrowserThread::DB));
 
   DCHECK(!migrate_tried_);
   DCHECK_EQ(app_string_, kGnomeKeyringAppString);
 
   // Record the fact that we've attempted migration already right away, so that
   // we don't get recursive calls back to MigrateToProfileSpecificLogins().
@@ skipping 22 matching lines @@
     // Each other profile must be able to migrate the shared data as well,
     // so we must leave it alone. After a few releases, we'll add code to
     // delete them, and eventually remove this migration code.
     // TODO(mdm): follow through with the plan above.
     PasswordStoreX::SetPasswordsUseLocalProfileId(prefs_);
   } else {
     // We failed to migrate for some reason. Use the old app string.
     app_string_ = kGnomeKeyringAppString;
   }
 }