Remove calls to MessageLoop::current() in ipc.

Remove calls to MessageLoop::current() in ipc.

Why?
The fact that there's a MessageLoop on the thread is an
unnecessary implementation detail. When browser threads
are migrated to base/task_scheduler, tasks will no longer
have access to a MessageLoop.

These changes were generated manually.

BUG=616447
R=jam@chromium.org

Committed: https://crrev.com/bcb9b32ec79d574c921ba5ad8b9405d99d9d5f86
Cr-Commit-Position: refs/heads/master@{#400762}

[jam, 2016-06-20 19:34:20]

lgtm

[fdoray, 2016-06-20 19:40:54]

The CQ bit was checked by fdoray@chromium.org

[commit-bot: I haz the power, 2016-06-20 19:41:32]

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

[commit-bot: I haz the power, 2016-06-20 20:24:33]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-06-20 20:28:38]

Description was changed from

==========
Remove calls to MessageLoop::current() in ipc.

Why?
The fact that there's a MessageLoop on the thread is an
unnecessary implementation detail. When browser threads
are migrated to base/task_scheduler, tasks will no longer
have access to a MessageLoop.

These changes were generated manually.

BUG=616447
R=jam@chromium.org
==========

to

==========
Remove calls to MessageLoop::current() in ipc.

Why?
The fact that there's a MessageLoop on the thread is an
unnecessary implementation detail. When browser threads
are migrated to base/task_scheduler, tasks will no longer
have access to a MessageLoop.

These changes were generated manually.

BUG=616447
R=jam@chromium.org

Committed: https://crrev.com/bcb9b32ec79d574c921ba5ad8b9405d99d9d5f86
Cr-Commit-Position: refs/heads/master@{#400762}
==========

[commit-bot: I haz the power, 2016-06-20 20:28:39]

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