[device] Replace MessageLoopProxy usage with ThreadTaskRunnerHandle

Replace MessageLoopProxy usage with ThreadTaskRunnerHandle in device module.

MessageLoopProxy is deprecated.
This basically does a search and replace:

MessageLoopProxy::current() -> ThreadTaskRunnerHandle::Get().

BUG=391045
Committed: https://crrev.com/d4d2fc18bd3c078917e0ab952a786947a4daff27
Cr-Commit-Position: refs/heads/master@{#327237}

[Pranay, 2015-04-27 13:51:36]

pranay.kumar@samsung.com changed reviewers:
+ rockot@chromium.org

[Pranay, 2015-04-27 13:51:36]

PTAL

[Ken Rockot(use gerrit already), 2015-04-28 03:19:09]

Thanks for doing this! A few problems:

This has SingleThreadedTaskRunners all over the place named foo_message_loop.
Please change to foo_task_runner.

Also see comment below.

https://codereview.chromium.org/1107013002/diff/1/device/serial/serial_connec...
File device/serial/serial_connection_unittest.cc (right):

https://codereview.chromium.org/1107013002/diff/1/device/serial/serial_connec...
device/serial/serial_connection_unittest.cc:73: base::ThreadTaskRunnerHandle
Please fix the formatting here. How does this even compile?

[Pranay, 2015-04-28 04:32:11]

On 2015/04/28 03:19:09, Ken Rockot wrote:
> Thanks for doing this! A few problems:
> 
> This has SingleThreadedTaskRunners all over the place named foo_message_loop.
> Please change to foo_task_runner.
> 
> Also see comment below.
> 
>
https://codereview.chromium.org/1107013002/diff/1/device/serial/serial_connec...
> File device/serial/serial_connection_unittest.cc (right):
> 
>
https://codereview.chromium.org/1107013002/diff/1/device/serial/serial_connec...
> device/serial/serial_connection_unittest.cc:73: base::ThreadTaskRunnerHandle
> Please fix the formatting here. How does this even compile?

Hi Ken,

Thanks for reviewing this patch. I have updated the patch w.r.t your inputs.
Please take a look :)

[Ken Rockot(use gerrit already), 2015-04-28 05:02:02]

lgtm

https://codereview.chromium.org/1107013002/diff/20001/device/serial/serial_co...
File device/serial/serial_connection_factory.h (right):

https://codereview.chromium.org/1107013002/diff/20001/device/serial/serial_co...
device/serial/serial_connection_factory.h:12: #include
"base/message_loop/message_loop_proxy.h"
Oops, missed this before. Please also remove uses of this header where possible.
There are a few places.

[Pranay, 2015-04-28 05:11:36]

Thanks Ken,
updated the changes :)

[Pranay, 2015-04-28 05:11:41]

The CQ bit was checked by pranay.kumar@samsung.com

[Pranay, 2015-04-28 05:11:41]

The patchset sent to the CQ was uploaded after l-g-t-m from rockot@chromium.org
Link to the patchset: https://codereview.chromium.org/1107013002/#ps40001
(title: "Fixed Review Comments : Removal of message_loop_proxy header file")

[commit-bot: I haz the power, 2015-04-28 05:11:52]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1107013002/40001

[commit-bot: I haz the power, 2015-04-28 06:08:29]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2015-04-28 06:09:21]

Patchset 3 (id:??) landed as
https://crrev.com/d4d2fc18bd3c078917e0ab952a786947a4daff27
Cr-Commit-Position: refs/heads/master@{#327237}

[Pranay, 2015-05-04 03:25:23]

Done

https://codereview.chromium.org/1107013002/diff/1/device/serial/serial_connec...
File device/serial/serial_connection_unittest.cc (right):

https://codereview.chromium.org/1107013002/diff/1/device/serial/serial_connec...
device/serial/serial_connection_unittest.cc:73: base::ThreadTaskRunnerHandle
On 2015/04/28 03:19:09, Ken Rockot wrote:
> Please fix the formatting here. How does this even compile?

Done.

https://codereview.chromium.org/1107013002/diff/20001/device/serial/serial_co...
File device/serial/serial_connection_factory.h (right):

https://codereview.chromium.org/1107013002/diff/20001/device/serial/serial_co...
device/serial/serial_connection_factory.h:12: #include
"base/message_loop/message_loop_proxy.h"
On 2015/04/28 05:02:02, Ken Rockot wrote:
> Oops, missed this before. Please also remove uses of this header where
possible.
> There are a few places.

Done.