Revert of Remove ganesh whitelist for all Android Lollipop devices

Revert of Remove ganesh whitelist for all Android Lollipop devices (patchset #2 id:20001 of https://codereview.chromium.org/982153002/)

Reason for revert:
This unintentionally blacklisted nexus 6.

Original issue's description:
> Remove ganesh whitelist for all Android Lollipop devices
> 
> Some old devices are getting lollipop update without updated drivers.
> 
> BUG=
> 
> Committed: https://crrev.com/9685ef41ca89943d9e918f5bd7636323bec38af0
> Cr-Commit-Position: refs/heads/master@{#319762}

BUG=443060
TBR=aelias,zmo

[boliu, 2015-03-11 23:30:37]

Created Revert of Remove ganesh whitelist for all Android Lollipop devices

[boliu, 2015-03-11 23:31:39]

Removed all the NOTRYs and whatnot, but question, should I bump the version, or
reverting that is fine as well?

[boliu, 2015-03-11 23:59:07]

On 2015/03/11 23:31:39, boliu wrote:
> Removed all the NOTRYs and whatnot, but question, should I bump the version,
or
> reverting that is fine as well?

My change is still the last change to this file, so I don't think it's worth
worrying about versioning here. TBR-ing

[boliu, 2015-03-11 23:59:29]

The CQ bit was checked by boliu@chromium.org

[commit-bot: I haz the power, 2015-03-12 00:00:56]

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

[vmiura, 2015-03-12 01:38:54]

I was going to say, if we use this version number for UMA reports or something
like that, it may be better to change it - that way when someone makes the next
change they don't use the same number as the one you used in the patch.

[boliu, 2015-03-12 01:39:40]

The CQ bit was unchecked by boliu@chromium.org

[boliu, 2015-03-12 01:40:09]

On 2015/03/12 01:38:54, vmiura wrote:
> I was going to say, if we use this version number for UMA reports or something
> like that, it may be better to change it - that way when someone makes the
next
> change they don't use the same number as the one you used in the patch.

-cq

I'll update the version tomorrow

[aelias_OOO_until_Jul13, 2015-03-12 02:30:21]

Do we know why the Nexus 6 isn't covered under the K + OpenGL ES 3 rule?

[vmiura, 2015-03-12 14:48:27]

On 2015/03/12 02:30:21, aelias wrote:
> Do we know why the Nexus 6 isn't covered under the K + OpenGL ES 3 rule?

Their GL version string wasn't parsed correctly.

Fixed here (crrev.com/999983002) so we could abandon this revert.

[boliu, 2015-03-12 16:30:09]

On 2015/03/12 14:48:27, vmiura wrote:
> On 2015/03/12 02:30:21, aelias wrote:
> > Do we know why the Nexus 6 isn't covered under the K + OpenGL ES 3 rule?
> 
> Their GL version string wasn't parsed correctly.
> 
> Fixed here (crrev.com/999983002) so we could abandon this revert.

Thanks Victor!

I guess the question is how many devices fell into the parsing error, but was
not on L already, which now gets ganesh whitelisted. Probably fine I imagine,
but something to think about..

[vmiura, 2015-03-12 17:59:50]

On 2015/03/12 16:30:09, boliu wrote:
> On 2015/03/12 14:48:27, vmiura wrote:
> > On 2015/03/12 02:30:21, aelias wrote:
> > > Do we know why the Nexus 6 isn't covered under the K + OpenGL ES 3 rule?
> > 
> > Their GL version string wasn't parsed correctly.
> > 
> > Fixed here (crrev.com/999983002) so we could abandon this revert.
> 
> Thanks Victor!
> 
> I guess the question is how many devices fell into the parsing error, but was
> not on L already, which now gets ganesh whitelisted. Probably fine I imagine,
> but something to think about..

Yes, I'm going to try to get UMA stats on what devices are getting blacklisted.