cc: remove call to SkImageFilter::canFilterImageGPU().

cc: remove call to SkImageFilter::canFilterImageGPU().

This function is going away in Skia, and probably doesn't do what the
caller (added in https://codereview.chromium.org/21154002/) intended
anyway: it means that the filter implements filterImageGPU(), an
explicit GPU path which draws texture-to-texture. The filter may
return false for canFilterImageGPU(), and still happily run on the GPU
using generic Skia calls in onFilterImage().

Anyway, all of this confusion will soon be removed, along with these
functions.

R=ajuma@chromium.org

BUG=
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

Committed: https://crrev.com/86649e2861205f8ce4d7099cb83b1cd16648dfa8
Cr-Commit-Position: refs/heads/master@{#387930}

[Stephen White, 2016-04-18 14:44:24]

Description was changed from

==========
cc: remove call to SkImageFilter::canFilterImageGPU().

This function is going away in Skia, and probably doesn't do what the
caller (added in https://codereview.chromium.org/21154002/) intended
anyway: it means that the filter implements filterImageGPU(), an
explicit GPU path which draws texture-to-texture. The filter may
return false for canFilterImageGPU(), and still happily run on the GPU
using generic Skia calls in onFilterImage().

Anyway, all of this confusion will soon be removed, along with these
functions.

R=ajuma@chromium.org

BUG=
==========

to

==========
cc: remove call to SkImageFilter::canFilterImageGPU().

This function is going away in Skia, and probably doesn't do what the
caller (added in https://codereview.chromium.org/21154002/) intended
anyway: it means that the filter implements filterImageGPU(), an
explicit GPU path which draws texture-to-texture. The filter may
return false for canFilterImageGPU(), and still happily run on the GPU
using generic Skia calls in onFilterImage().

Anyway, all of this confusion will soon be removed, along with these
functions.

R=ajuma@chromium.org

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

[Stephen White, 2016-04-18 14:44:48]

Description was changed from

==========
cc: remove call to SkImageFilter::canFilterImageGPU().

This function is going away in Skia, and probably doesn't do what the
caller (added in https://codereview.chromium.org/21154002/) intended
anyway: it means that the filter implements filterImageGPU(), an
explicit GPU path which draws texture-to-texture. The filter may
return false for canFilterImageGPU(), and still happily run on the GPU
using generic Skia calls in onFilterImage().

Anyway, all of this confusion will soon be removed, along with these
functions.

R=ajuma@chromium.org

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

to

==========
cc: remove call to SkImageFilter::canFilterImageGPU().

This function is going away in Skia, and probably doesn't do what the
caller (added in https://codereview.chromium.org/21154002/) intended
anyway: it means that the filter implements filterImageGPU(), an
explicit GPU path which draws texture-to-texture. The filter may
return false for canFilterImageGPU(), and still happily run on the GPU
using generic Skia calls in onFilterImage().

Anyway, all of this confusion will soon be removed, along with these
functions.

R=ajuma@chromium.org

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

[Stephen White, 2016-04-18 14:45:04]

Ali: PTAL. Thanks!

[Stephen White, 2016-04-18 14:45:19]

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

[commit-bot: I haz the power, 2016-04-18 14:45:35]

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

[commit-bot: I haz the power, 2016-04-18 15:46:18]

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

[commit-bot: I haz the power, 2016-04-18 15:46:18]

Dry run: This issue passed the CQ dry run.

[ajuma, 2016-04-18 16:41:48]

lgtm

[ajuma, 2016-04-18 16:41:53]

The CQ bit was checked by ajuma@chromium.org

[commit-bot: I haz the power, 2016-04-18 16:42:14]

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

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

Description was changed from

==========
cc: remove call to SkImageFilter::canFilterImageGPU().

This function is going away in Skia, and probably doesn't do what the
caller (added in https://codereview.chromium.org/21154002/) intended
anyway: it means that the filter implements filterImageGPU(), an
explicit GPU path which draws texture-to-texture. The filter may
return false for canFilterImageGPU(), and still happily run on the GPU
using generic Skia calls in onFilterImage().

Anyway, all of this confusion will soon be removed, along with these
functions.

R=ajuma@chromium.org

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

to

==========
cc: remove call to SkImageFilter::canFilterImageGPU().

This function is going away in Skia, and probably doesn't do what the
caller (added in https://codereview.chromium.org/21154002/) intended
anyway: it means that the filter implements filterImageGPU(), an
explicit GPU path which draws texture-to-texture. The filter may
return false for canFilterImageGPU(), and still happily run on the GPU
using generic Skia calls in onFilterImage().

Anyway, all of this confusion will soon be removed, along with these
functions.

R=ajuma@chromium.org

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

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

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-04-18 17:21:30]

Description was changed from

==========
cc: remove call to SkImageFilter::canFilterImageGPU().

This function is going away in Skia, and probably doesn't do what the
caller (added in https://codereview.chromium.org/21154002/) intended
anyway: it means that the filter implements filterImageGPU(), an
explicit GPU path which draws texture-to-texture. The filter may
return false for canFilterImageGPU(), and still happily run on the GPU
using generic Skia calls in onFilterImage().

Anyway, all of this confusion will soon be removed, along with these
functions.

R=ajuma@chromium.org

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

to

==========
cc: remove call to SkImageFilter::canFilterImageGPU().

This function is going away in Skia, and probably doesn't do what the
caller (added in https://codereview.chromium.org/21154002/) intended
anyway: it means that the filter implements filterImageGPU(), an
explicit GPU path which draws texture-to-texture. The filter may
return false for canFilterImageGPU(), and still happily run on the GPU
using generic Skia calls in onFilterImage().

Anyway, all of this confusion will soon be removed, along with these
functions.

R=ajuma@chromium.org

BUG=
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

Committed: https://crrev.com/86649e2861205f8ce4d7099cb83b1cd16648dfa8
Cr-Commit-Position: refs/heads/master@{#387930}
==========

[commit-bot: I haz the power, 2016-04-18 17:21:31]

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