cc: Remove the RenderPassId field from AppendQuadsData.

cc/test/layer_test_common.cc

Index: cc/test/layer_test_common.cc
diff --git a/cc/test/layer_test_common.cc b/cc/test/layer_test_common.cc
index 99d3c1c06996a613ad9e3907230ed7c534d74e01..e26206cffc4f914760418405992e68ac1a9c2f7e 100644
--- a/cc/test/layer_test_common.cc
+++ b/cc/test/layer_test_common.cc
@@ -137,19 +137,19 @@ void LayerTestCommon::LayerImplTest::AppendQuadsWithOcclusion(
 
 void LayerTestCommon::LayerImplTest::AppendQuadsForPassWithOcclusion(

[vmpstr, 2015/01/28 22:05:27]

Should the rest of the functions also take a render_pass instead of using
|render_pass_|? It's not a big concern since this is test, but it's pretty easy
in this function to accidentally use render_pass_ instead of render_pass

[danakj, 2015/01/28 22:06:21]

We could, it would just mean a bunch of code at callsites creating renderpasses
to pass in. I could rename the local variable if that helps?

     LayerImpl* layer_impl,
-    const RenderPassId& id,
+    RenderPass* render_pass,
     const gfx::Rect& occluded) {
-  AppendQuadsData data(id);
+  AppendQuadsData data;
 
-  render_pass_->quad_list.clear();
-  render_pass_->shared_quad_state_list.clear();
+  render_pass->quad_list.clear();
+  render_pass->shared_quad_state_list.clear();
 
   Occlusion occlusion(layer_impl->draw_transform(),
                       SimpleEnclosedRegion(occluded),
                       SimpleEnclosedRegion());
 
   layer_impl->WillDraw(DRAW_MODE_HARDWARE, resource_provider());
-  layer_impl->AppendQuads(render_pass_.get(), occlusion, &data);
+  layer_impl->AppendQuads(render_pass, occlusion, &data);
   layer_impl->DidDraw(resource_provider());
 }