commit e24da966b14e5b952ee11a7d13bb1539be2a5c8e
author Dan Stoza <stoza@google.com> Tue Jun 21 15:02:23 2016 -0700
committer Dan Stoza <stoza@google.com> Tue Jun 21 15:02:23 2016 -0700
tree dbd938532550049663bfd3583bc4a908aa65cad0
parent f9d7e1a0aa05bb47527f054b85a36f16e7955088

HWC2: Don't set null handle for client layers

Removes the code that explicitly set a null buffer handle for client
layers.

Bug: 29463310
Change-Id: I570e6041ba72d64971bb6c364e8e7b6f84eeff08

services/surfaceflinger/Layer.cpp

diff --git a/services/surfaceflinger/Layer.cpp b/services/surfaceflinger/Layer.cpp
index d732c07..6c78000 100644
--- a/services/surfaceflinger/Layer.cpp
+++ b/services/surfaceflinger/Layer.cpp
@@ -726,11 +726,6 @@
         // setup a solid color layer yet
         ALOGV("[%s] Requesting Client composition", mName.string());
         setCompositionType(hwcId, HWC2::Composition::Client);
-        error = hwcLayer->setBuffer(nullptr, Fence::NO_FENCE);
-        if (error != HWC2::Error::None) {
-            ALOGE("[%s] Failed to set null buffer: %s (%d)", mName.string(),
-                    to_string(error).c_str(), static_cast<int32_t>(error));
-        }
         return;
     }