Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Ben Widawsky <ben@bwidawsk.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Fix gem_gtt_cpu_tlb
Date: Fri, 17 Aug 2012 10:13:34 +0200	[thread overview]
Message-ID: <20120817081334.GB5410@phenom.ffwll.local> (raw)
In-Reply-To: <1345183977-1113-1-git-send-email-ben@bwidawsk.net>

On Thu, Aug 16, 2012 at 11:12:57PM -0700, Ben Widawsky wrote:
> Revert "agp/intel, drm/i915: Use a write-combining map for updating PTEs"
> 
> This reverts commit 15a80851c8166c05c6f600fede1719b29eb70737.
> 
> I haven't spent any time looking at the patch but bisection and revert
> testing proves this fixes the issues. Begone ye ext4 errors!
> 
> Signed-off-by: Ben Widawsky <ben@bwidawsk.net>

Patched removed from dinq, thanks a lot to you (and Paulo) for digging
this out.
-Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

  reply	other threads:[~2012-08-17  8:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-17  6:12 [PATCH] drm/i915: Fix gem_gtt_cpu_tlb Ben Widawsky
2012-08-17  8:13 ` Daniel Vetter [this message]
2012-08-18 10:33   ` Chris Wilson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120817081334.GB5410@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=ben@bwidawsk.net \
    --cc=intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox