From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Wilson Subject: Kill the flushing list Date: Thu, 12 Jul 2012 16:13:33 +0100 Message-ID: <1342106019-17806-1-git-send-email-chris@chris-wilson.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from fireflyinternet.com (smtp.fireflyinternet.com [109.228.6.236]) by gabe.freedesktop.org (Postfix) with ESMTP id A25B69E769 for ; Thu, 12 Jul 2012 08:14:13 -0700 (PDT) Received: from arrandale.alporthouse.com (unverified [78.156.66.37]) by fireflyinternet.com (Firefly Internet SMTP) with ESMTP id 118118975-1500050 for ; Thu, 12 Jul 2012 16:14:09 +0100 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org So it appears I alone have been hitting the WARNs left inplace to flag breakage from the initial prep work for the flushing list. Thanks to this dubious honour, I've reviewed that work and decided to finish the removal in order to kill the WARNs. Please review, review, test, review. -Chris