cc: Remove ScopedReadLockGpuMemoryBuffer

cc: Remove ScopedReadLockGpuMemoryBuffer

This approach is not going to be used.

BUG=608026
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

Committed: https://crrev.com/60af4caf9047de95048aeb2bf4e3cee9e317c62e
Cr-Commit-Position: refs/heads/master@{#400759}

[ccameron, 2016-06-20 19:25:13]

Description was changed from

==========
cc: Remove ScopedReadLockGpuMemoryBuffer

This approach is not going to be used.

BUG=608026
==========

to

==========
cc: Remove ScopedReadLockGpuMemoryBuffer

This approach is not going to be used.

BUG=608026
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
==========

[ccameron, 2016-06-20 19:27:17]

ccameron@chromium.org changed reviewers:
+ erikchen@chromium.org

[ccameron, 2016-06-20 19:27:17]

I checked with reveman, and he is not planning to use
CreateGpuMemoryBufferFromClientId, so I might as well remove it. This gets rid
of the one caller.

[erikchen, 2016-06-20 19:28:50]

lgtm

[ccameron, 2016-06-20 19:29:51]

The CQ bit was checked by ccameron@chromium.org

[commit-bot: I haz the power, 2016-06-20 19:30:11]

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

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

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-06-20 20:22:54]

Description was changed from

==========
cc: Remove ScopedReadLockGpuMemoryBuffer

This approach is not going to be used.

BUG=608026
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
==========

to

==========
cc: Remove ScopedReadLockGpuMemoryBuffer

This approach is not going to be used.

BUG=608026
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

Committed: https://crrev.com/60af4caf9047de95048aeb2bf4e3cee9e317c62e
Cr-Commit-Position: refs/heads/master@{#400759}
==========

[commit-bot: I haz the power, 2016-06-20 20:22:54]

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