GLES2CmdDecoder should resize GLSurface using GLSurface::Resize

GLES2CmdDecoder should resize GLSurface using GLSurface::Resize

A special resize callback is unnecessary because the decoder has access to the GLSurface and can call Resize on that.

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

[jbauman, 2015-10-26 23:30:29]

Description was changed from

==========
GLES2CmdDecoder should resize Surface using GLSurface::Resize

A special resize callback is unnecessary because the decoder has access to the
GLSurface and can call Resize on that.
==========

to

==========
GLES2CmdDecoder should resize Surface using GLSurface::Resize

A special resize callback is unnecessary because the decoder has access to the
GLSurface and can call Resize on that.
==========

[jbauman, 2015-10-27 02:09:35]

Description was changed from

==========
GLES2CmdDecoder should resize Surface using GLSurface::Resize

A special resize callback is unnecessary because the decoder has access to the
GLSurface and can call Resize on that.
==========

to

==========
GLES2CmdDecoder should resize GLSurface using GLSurface::Resize

A special resize callback is unnecessary because the decoder has access to the
GLSurface and can call Resize on that.
==========

[jbauman, 2015-10-27 20:52:45]

jbauman@chromium.org changed reviewers:
+ piman@chromium.org

[piman, 2015-10-27 23:11:47]

LGTM overall, but one thing.

https://codereview.chromium.org/1420503011/diff/90001/content/common/gpu/imag...
File content/common/gpu/image_transport_surface_android.cc (right):

https://codereview.chromium.org/1420503011/diff/90001/content/common/gpu/imag...
content/common/gpu/image_transport_surface_android.cc:30:
GpuMemoryManager::kScheduleManageNow);
So, because of crbug.com/526196 , and after
https://codereview.chromium.org/1324413003 , this doesn't do anything anymore
actually (the GpuMemoryManager doesn't have clients to manage any more). Sohan
is kind of on the hook to remove those GpuMemoryManager bits as a follow-up but
it hasn't happened yet.
But bottom line, I think we can just remove this class (and
PassThroughImageTransportSurface::manager_ while we're at it).

[jbauman, 2015-10-28 21:29:16]

jbauman@chromium.org changed reviewers:
+ sky@chromium.org

[jbauman, 2015-10-28 21:29:17]

sky@: OWNERS review of components/mus.

[sky, 2015-10-29 15:23:14]

LGTM

[jbauman, 2015-10-29 20:34:12]

The CQ bit was checked by jbauman@chromium.org

[jbauman, 2015-10-29 20:34:13]

The patchset sent to the CQ was uploaded after l-g-t-m from piman@chromium.org
Link to the patchset: https://codereview.chromium.org/1420503011/#ps130001
(title: " ")

[commit-bot: I haz the power, 2015-10-29 20:34:42]

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

[commit-bot: I haz the power, 2015-10-29 22:01:41]

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

[commit-bot: I haz the power, 2015-10-29 22:01:42]

Try jobs failed on following builders:
  win_chromium_x64_rel_ng on tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[jbauman, 2015-10-30 02:01:00]

The CQ bit was checked by jbauman@chromium.org

[commit-bot: I haz the power, 2015-10-30 02:02:24]

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

[commit-bot: I haz the power, 2015-10-30 02:34:05]

Committed patchset #8 (id:130001)

[commit-bot: I haz the power, 2015-10-30 02:34:51]

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