Remove potential unsatisfied linker error.

Remove potential unsatisfied linker error.

BUG=543201
NOTRY=true

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

[Peter Wen, 2016-01-26 18:30:21]

wnwen@chromium.org changed reviewers:
+ yfriedman@chromium.org

[Peter Wen, 2016-01-26 18:30:21]

Hi Yaron and Ted,

Removing this potential exception for now. Will add it with a guard in the
follow up CL here: http://crrev.com/1634903002

Thanks,

Peter

[Yaron, 2016-01-26 18:30:49]

lgtm

[Ted C, 2016-01-26 18:43:54]

tedchoc@chromium.org changed reviewers:
+ tedchoc@chromium.org

[Ted C, 2016-01-26 18:43:54]

lgtm

[Peter Wen, 2016-01-26 19:37:01]

The CQ bit was checked by wnwen@chromium.org

[Peter Wen, 2016-01-26 19:37:37]

Description was changed from

==========
Remove potential unsatisfied linker error.

BUG=543201
==========

to

==========
Remove potential unsatisfied linker error.

BUG=543201
NOTRY=true
==========

[Peter Wen, 2016-01-26 19:37:41]

The CQ bit was unchecked by wnwen@chromium.org

[Peter Wen, 2016-01-26 19:37:41]

The CQ bit was checked by wnwen@chromium.org

[commit-bot: I haz the power, 2016-01-26 19:38:05]

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

[commit-bot: I haz the power, 2016-01-26 19:44:20]

Description was changed from

==========
Remove potential unsatisfied linker error.

BUG=543201
NOTRY=true
==========

to

==========
Remove potential unsatisfied linker error.

BUG=543201
NOTRY=true
==========

[commit-bot: I haz the power, 2016-01-26 19:44:20]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-01-26 19:45:44]

Description was changed from

==========
Remove potential unsatisfied linker error.

BUG=543201
NOTRY=true
==========

to

==========
Remove potential unsatisfied linker error.

BUG=543201
NOTRY=true

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

[commit-bot: I haz the power, 2016-01-26 19:45:44]

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

[jbudorick, 2016-01-26 20:30:45]

On 2016/01/26 19:45:44, commit-bot: I haz the power wrote:
> Patchset 1 (id:??) landed as
> https://crrev.com/bf9913493217d1821c8fdb7bbb18afa9e6b4f76d
> Cr-Commit-Position: refs/heads/master@{#371564}

NOTRY? :(

[Peter Wen, 2016-01-26 20:31:54]

On 2016/01/26 20:30:45, jbudorick wrote:
> On 2016/01/26 19:45:44, commit-bot: I haz the power wrote:
> > Patchset 1 (id:??) landed as
> > https://crrev.com/bf9913493217d1821c8fdb7bbb18afa9e6b4f76d
> > Cr-Commit-Position: refs/heads/master@{#371564}
> 
> NOTRY? :(

Sorry, John. Thought nothing depended on this so didn't want to waste the try
jobs. :(

Will run next time even if I think otherwise, just in case.