Properly route screen orientation IPC messages.

content/renderer/screen_orientation/screen_orientation_dispatcher.cc

Index: content/renderer/screen_orientation/screen_orientation_dispatcher.cc
diff --git a/content/renderer/screen_orientation/screen_orientation_dispatcher.cc b/content/renderer/screen_orientation/screen_orientation_dispatcher.cc
index 91a36e39767de436b22bddca44c9f9a8a076e283..e67cc73634ec79a3541815223011e5f6d3f4f661 100644
--- a/content/renderer/screen_orientation/screen_orientation_dispatcher.cc
+++ b/content/renderer/screen_orientation/screen_orientation_dispatcher.cc
@@ -69,12 +69,13 @@ void ScreenOrientationDispatcher::lockOrientation(
   CancelPendingLocks();
 
   int request_id = pending_callbacks_.Add(callback);
-  Send(new ScreenOrientationHostMsg_LockRequest(orientation, request_id));
+  Send(new ScreenOrientationHostMsg_LockRequest(
+      routing_id(), orientation, request_id));

[jam, 2014/06/11 00:42:49]

looks like this is based of changes that haven't landed. can you make it based
off trunk? it makes it harder to review otherwise

[mlamouri (slow - plz ping), 2014/06/16 14:11:54]

Actually, it was based on another change that you reviewed, that's why I assumed
it would be fine. Let me know what procedure you prefer me to follow when I have
two CLs with a dependency.

 }
 
 void ScreenOrientationDispatcher::unlockOrientation() {
   CancelPendingLocks();
-  Send(new ScreenOrientationHostMsg_Unlock);
+  Send(new ScreenOrientationHostMsg_Unlock(routing_id()));
 }
 
 }  // namespace content