More build config cleanup.

ui/gl/sync_control_vsync_provider.cc

Index: ui/gl/sync_control_vsync_provider.cc
diff --git a/ui/gl/sync_control_vsync_provider.cc b/ui/gl/sync_control_vsync_provider.cc
index 66d3734f58e4fd114c671776287400df6014bba2..2b9453bef3568e9fec6e9486299f60382e2e9341 100644
--- a/ui/gl/sync_control_vsync_provider.cc
+++ b/ui/gl/sync_control_vsync_provider.cc
@@ -125,17 +125,7 @@ void SyncControlVSyncProvider::GetVSyncParameters(
     if (relative_change < kRelativeIntervalDifferenceThreshold) {
       if (new_interval.InMicroseconds() < kMinVsyncIntervalUs ||
           new_interval.InMicroseconds() > kMaxVsyncIntervalUs) {
-#if defined(USE_ASH)

[jamesr, 2015/12/11 19:17:00]

hm, wasn't USE_ASH true before? are you sure changing this LOG(ERROR) into a
LOG(FATAL) on linux and fnl works?

[viettrungluu, 2015/12/11 19:28:19]

"Fixed".

-        // On ash platforms (ChromeOS essentially), the real refresh interval is
-        // queried from XRandR, regardless of the value calculated here, and
-        // this value is overriden by ui::CompositorVSyncManager.  The log
-        // should not be fatal in this case. Reconsider all this when XRandR
-        // support is added to non-ash platforms.
-        // http://crbug.com/340851
-        LOG(ERROR)
-#else
         LOG(FATAL)
-#endif  // USE_ASH
             << "Calculated bogus refresh interval="
             << new_interval.InMicroseconds()
             << " us., last_timebase_=" << last_timebase_.ToInternalValue()