From: Keith Packard <keithp@keithp.com>
To: "Woodhouse, David" <david.woodhouse@intel.com>,
Ben Widawsky <ben@bwidawsk.net>
Cc: Dave Airlie <airlied@redhat.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>, "Qu, Yan" <yan.qu@intel.com>
Subject: Re: [PATCH v4 0/4] ILK VT-d fix
Date: Mon, 24 Oct 2011 08:37:26 -0700 [thread overview]
Message-ID: <yunipnejt8p.fsf@aiko.keithp.com> (raw)
In-Reply-To: <1319443974.13738.85.camel@shinybook.infradead.org>
[-- Attachment #1.1: Type: text/plain, Size: 396 bytes --]
On Mon, 24 Oct 2011 08:14:45 +0000, "Woodhouse, David" <david.woodhouse@intel.com> wrote:
> The IOMMU patches are now in Linus' tree and thus will be in the 3.1
> release. Are we going to push the graphics patches in time for the 3.1
> release too?
The graphics patches are in the 3.2 pull request; they'll be available
for the 3.1 stable series though.
--
keith.packard@intel.com
[-- Attachment #1.2: Type: application/pgp-signature, Size: 827 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2011-10-24 15:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-15 20:47 [PATCH v4 0/4] ILK VT-d fix Ben Widawsky
2011-10-15 20:47 ` [PATCH 1/4] intel-iommu: Workaround IOTLB hang on Ironlake GPU Ben Widawsky
2011-10-15 20:47 ` [PATCH 2/4] intel-iommu: Export a flag indicating that the IOMMU is used for iGFX Ben Widawsky
2011-10-15 20:47 ` [PATCH 3/4] drm/i915: Remove early exit on i915_gpu_idle Ben Widawsky
2011-10-15 20:59 ` Daniel Vetter
2011-10-15 22:10 ` Chris Wilson
2011-10-15 20:47 ` [PATCH 4/4] drm/i915: ILK + VT-d workaround Ben Widawsky
2011-10-15 21:15 ` Daniel Vetter
2011-10-15 22:09 ` Chris Wilson
[not found] ` <1319443974.13738.85.camel@shinybook.infradead.org>
2011-10-24 15:37 ` Keith Packard [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=yunipnejt8p.fsf@aiko.keithp.com \
--to=keithp@keithp.com \
--cc=airlied@redhat.com \
--cc=ben@bwidawsk.net \
--cc=david.woodhouse@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=yan.qu@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.