evdev: Fix infinite loop when devices are unplugged

ui/events/ozone/event_converter_ozone.h

Index: ui/events/ozone/event_converter_ozone.h
diff --git a/ui/events/ozone/event_converter_ozone.h b/ui/events/ozone/event_converter_ozone.h
index 90826c26580d341ab94c7116edea219315ea51de..4dd99edd5dee9c8bc953afc256537b1387ab85ec 100644
--- a/ui/events/ozone/event_converter_ozone.h
+++ b/ui/events/ozone/event_converter_ozone.h
@@ -6,25 +6,26 @@
 #define UI_EVENTS_OZONE_EVENT_CONVERTER_OZONE_H_
 
 #include "base/memory/scoped_ptr.h"
-#include "base/message_loop/message_pump_libevent.h"
 #include "ui/events/events_export.h"
 
 namespace ui {
 class Event;
 
-// In ozone, Chrome reads events from file descriptors created from Linux device
-// drivers. The |MessagePumpLibevent::Watcher| parent class provides the
-// functionality to watch a file descriptor for the arrival of new data and
-// notify its subclasses. Device-specific event converters turn bytes read from
-// the file descriptor into |ui::Event| instances. This class provides the
-// functionality needed in common across all converters: dispatching the
-// |ui::Event| to aura.
-class EVENTS_EXPORT EventConverterOzone
-    : public base::MessagePumpLibevent::Watcher {
+// Ozone implementations can generate input events in whatever way is
+// appropriate for the platform.
+// This class provides the functionality needed in common across all
+// converters: dispatching the |ui::Event| to aura.
+class EVENTS_EXPORT EventConverterOzone {
  public:
   EventConverterOzone();
   virtual ~EventConverterOzone();
 
+  // Start processing events.

[rjkroege, 2014/01/27 19:03:16]

Is it re-startable? I.e.: would one ever call Stop() and then later call
Start()?

Should Start and Stop be implicit on the constructor and destructor?

+  virtual void Start() = 0;
+
+  // Stop processing events.
+  virtual void Stop() = 0;
+
  protected:
   // Subclasses should use this method to post a task that will dispatch
   // |event| from the UI message loop. This method takes ownership of