Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753056Ab3EaDRB (ORCPT ); Thu, 30 May 2013 23:17:01 -0400 Received: from mail-la0-f44.google.com ([209.85.215.44]:37256 "EHLO mail-la0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752392Ab3EaDQ4 (ORCPT ); Thu, 30 May 2013 23:16:56 -0400 MIME-Version: 1.0 In-Reply-To: References: Date: Fri, 31 May 2013 13:16:54 +1000 Message-ID: Subject: Re: [PATCH v3 0/9] Clean up write-combining MTRR addition From: Dave Airlie To: Andy Lutomirski Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org, Daniel Vetter , Jerome Glisse , Alex Deucher Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1152 Lines: 25 On Fri, May 24, 2013 at 4:35 AM, Andy Lutomirski wrote: > On Mon, May 13, 2013 at 4:58 PM, Andy Lutomirski wrote: >> A fair number of drivers (mostly graphics) add write-combining MTRRs. >> Most ignore errors and most add the MTRR even on PAT systems which don't >> need to use MTRRs. >> >> This series adds new functions arch_phys_wc_{add,del} that, on PAT-less >> x86 systems with MTRRs, add MTRRs and report errors, and that do nothing >> otherwise. (Other architectures, if any, with a similar mechanism could >> implement them.) > > That's the path to upstream for this? Should it go through drm-next? > (Sorry for possible noob question -- I've never sent in anything other > than trivial fixes to drm stuff before.) I've pulled the v3 series into drm-next, lets see how they go for a while, I suppose I should try and boot an AGP box with them. Dave. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/