Make lost context and error message callbacks on GpuControl go to client

ppapi/proxy/ppapi_command_buffer_proxy.cc

Index: ppapi/proxy/ppapi_command_buffer_proxy.cc
diff --git a/ppapi/proxy/ppapi_command_buffer_proxy.cc b/ppapi/proxy/ppapi_command_buffer_proxy.cc
index c96b44af5565dd35070541565b36c7ca10f60d95..1b9c734c4d87042bca8d13fd7994c3b4b134e016 100644
--- a/ppapi/proxy/ppapi_command_buffer_proxy.cc
+++ b/ppapi/proxy/ppapi_command_buffer_proxy.cc
@@ -241,6 +241,11 @@ void PpapiCommandBufferProxy::SignalQuery(uint32_t query,
   NOTREACHED();
 }
 
+void PpapiCommandBufferProxy::SetGpuControlClient(gpu::GpuControlClient*) {
+  // There's no concept of lost context or error message for this implementation
+  // of GpuControl, so we don't bother to store the client.

[piman, 2016/04/11 21:54:26]

Actually, there is a lost context callback, but right now it doesn't flow here
(it flows directly to the plugin instance), so this is fine. I'll try to wire it
up properly as a follow-up. You can TODO(piman).

[danakj, 2016/04/11 22:27:32]

Done.

+}
+
 gpu::Capabilities PpapiCommandBufferProxy::GetCapabilities() {
   return capabilities_;
 }