DeviceSettingsProvider's write path uses OwnerSettingsService now.

components/ownership/owner_settings_service.h

Index: components/ownership/owner_settings_service.h
diff --git a/components/ownership/owner_settings_service.h b/components/ownership/owner_settings_service.h
index a642bf2870524200562d21c4d80ef95dbdb0b859..079807860537ed4b2b1edbed15923181c8f02532 100644
--- a/components/ownership/owner_settings_service.h
+++ b/components/ownership/owner_settings_service.h
@@ -87,6 +87,10 @@ class OWNERSHIP_EXPORT OwnerSettingsService : public KeyedService {
   // Sets |setting| value to |value|.
   virtual bool Set(const std::string& setting, const base::Value& value) = 0;
 

[Mattias Nissler (ping if slow), 2014/10/24 08:08:02]

Can we put a comment here saying that this function is a temporary way to deal
with the problem of getting the tentative device settings from before ownership
gets established into OwnershipSettingsServiceChromeOS? Might also be good to
rename this to CommitTentativeDeviceSettings or somesuch to make this more
clear.

+  // Sets policy.
+  virtual bool SetPolicy(
+      scoped_ptr<enterprise_management::PolicyData> policy) = 0;
+
   bool SetBoolean(const std::string& setting, bool value);
   bool SetInteger(const std::string& setting, int value);
   bool SetDouble(const std::string& setting, double value);