From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/3] drm/i915: bind driver to ValleyView chipsets
Date: Wed, 20 Jun 2012 13:56:27 -0700 [thread overview]
Message-ID: <20120620135627.5309dfed@jbarnes-desktop> (raw)
In-Reply-To: <20120620205356.GP7170@phenom.ffwll.local>
On Wed, 20 Jun 2012 22:53:56 +0200
Daniel Vetter <daniel@ffwll.ch> wrote:
> On Wed, Jun 20, 2012 at 10:53:13AM -0700, Jesse Barnes wrote:
> > With the code in place, we can bind the driver, should make bisect possible.
> >
> > Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
> Queued all three for -next, thanks for the respin.
Cool thanks. Sorry for the breakage to the read/write routines.
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2012-06-20 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 17:53 [PATCH 1/3] drm/i915: support page flipping on ValleyView Jesse Barnes
2012-06-20 17:53 ` [PATCH 2/3] drm/i915: enable display messages to GT " Jesse Barnes
2012-06-20 17:53 ` [PATCH 3/3] drm/i915: bind driver to ValleyView chipsets Jesse Barnes
2012-06-20 20:53 ` Daniel Vetter
2012-06-20 20:56 ` Jesse Barnes [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=20120620135627.5309dfed@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--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