Add DeviceMonitorLinux in BrowserMainLoop.

content/browser/devices_monitor/devices_monitor_mac.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.
+
+// This class implements content::DevicesMonitor on Mac.
+
+#ifndef CONTENT_BROWSER_DEVICES_MONITOR_DEVICES_MONITOR_MAC_H_
+#define CONTENT_BROWSER_DEVICES_MONITOR_DEVICES_MONITOR_MAC_H_
+
+#include "content/browser/devices_monitor/devices_monitor.h"
+
+namespace content {
+
+class DevicesMonitorMac : public DevicesMonitor {

[tommi (sloooow) - chröme, 2012/07/30 11:07:04]

do we need to add these empty classes now or can it wait until we have actual
implementations?  I think we might have an iteration or two on the linux
implementation before the interfaces are fully finalized and it would be good to
not have to go and maintain these empty classes.
Also, removing the empty classes makes this review shorter. :)

+ public:
+  DevicesMonitorMac();
+  virtual ~DevicesMonitorMac();
+
+  virtual void Start(base::SystemMonitor::DevicesChangedObserver*) OVERRIDE;
+  virtual void Stop(base::SystemMonitor::DevicesChangedObserver*) OVERRIDE;
+
+ private:
+  DISALLOW_COPY_AND_ASSIGN(DevicesMonitorMac);
+};
+
+}  // namespace content
+
+#endif  // CONTENT_BROWSER_DEVICES_MONITOR_DEVICES_MONITOR_MAC_H_