Namespace-qualify calls to logging::MakeCheckOpString

Namespace-qualify calls to logging::MakeCheckOpString

Otherwise, argument-dependent lookup will (given that the proper set
of headers are included at the same time) identify WebRTC's
rtc::MakeCheckOpString as an alternative to logging::MakeCheckOpString
if one of the function arguments are from the rtc:: namespace, making
the call ambiguous.

This was the reason why https://codereview.webrtc.org/2384693002 had
to be reverted.

Committed: https://crrev.com/1a928bccdd01937e89f6c89bca9ad4a8735f7542
Cr-Commit-Position: refs/heads/master@{#422905}

[kwiberg-chromium, 2016-10-04 14:59:28]

The CQ bit was checked by kwiberg@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-10-04 14:59:47]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[kwiberg-chromium, 2016-10-04 16:41:56]

kwiberg@chromium.org changed reviewers:
+ danakj@chromium.org

[kwiberg-chromium, 2016-10-04 16:41:56]

PTAL. Or redirect to the right person, if I arbitrarily selected the wrong
OWNER...

[commit-bot: I haz the power, 2016-10-04 16:57:03]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-10-04 16:57:04]

Dry run: This issue passed the CQ dry run.

[danakj, 2016-10-04 20:17:14]

LGTM

[danakj, 2016-10-04 20:17:18]

The CQ bit was checked by danakj@chromium.org

[commit-bot: I haz the power, 2016-10-04 20:17:52]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-10-04 20:25:04]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-10-04 20:29:01]

Description was changed from

==========
Namespace-qualify calls to logging::MakeCheckOpString

Otherwise, argument-dependent lookup will (given that the proper set
of headers are included at the same time) identify WebRTC's
rtc::MakeCheckOpString as an alternative to logging::MakeCheckOpString
if one of the function arguments are from the rtc:: namespace, making
the call ambiguous.

This was the reason why https://codereview.webrtc.org/2384693002 had
to be reverted.
==========

to

==========
Namespace-qualify calls to logging::MakeCheckOpString

Otherwise, argument-dependent lookup will (given that the proper set
of headers are included at the same time) identify WebRTC's
rtc::MakeCheckOpString as an alternative to logging::MakeCheckOpString
if one of the function arguments are from the rtc:: namespace, making
the call ambiguous.

This was the reason why https://codereview.webrtc.org/2384693002 had
to be reverted.

Committed: https://crrev.com/1a928bccdd01937e89f6c89bca9ad4a8735f7542
Cr-Commit-Position: refs/heads/master@{#422905}
==========

[commit-bot: I haz the power, 2016-10-04 20:29:02]

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