Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Widawsky <ben@bwidawsk.net>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Fix missed needs_dmar setting
Date: Thu, 13 Dec 2012 21:40:31 -0800	[thread overview]
Message-ID: <20121213214031.0000758e@unknown> (raw)
In-Reply-To: <20121213230007.GD5737@phenom.ffwll.local>

On Fri, 14 Dec 2012 00:00:07 +0100
Daniel Vetter <daniel@ffwll.ch> wrote:

> On Thu, Dec 13, 2012 at 11:47:47PM +0800, Zhenyu Wang wrote:
> > From Ben's AGP dependence removal change, "needs_dmar" flag has not
> > been properly setup for new chips using new GTT init function. This
> > one adds missed setting of that flag to make sure we do pci mappings
> > with IOMMU enabled.
> > 
> > Signed-off-by: Zhenyu Wang <zhenyuw@linux.intel.com>
> 
> Nice catch! Thanks for the patch, merged to -fixes for 3.8.
> -Daniel

dmar. can't live with it, can live without it

      reply	other threads:[~2012-12-14  5:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-13 15:47 [PATCH] drm/i915: Fix missed needs_dmar setting Zhenyu Wang
2012-12-13 23:00 ` Daniel Vetter
2012-12-14  5:40   ` Ben Widawsky [this message]

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=20121213214031.0000758e@unknown \
    --to=ben@bwidawsk.net \
    --cc=daniel@ffwll.ch \
    --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