From: Eric Anholt <eric@anholt.net>
To: Dave Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.sourceforge.net
Subject: Re: [PATCH 0/6] make gem_object embedable and convert i915 driver
Date: Tue, 13 Apr 2010 16:59:08 -0700 [thread overview]
Message-ID: <878w8qvr8z.fsf@pollan.anholt.net> (raw)
In-Reply-To: <o2g21d7e9971004122233i7ca9ed23y6277e4f6f9edf510@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1402 bytes --]
On Tue, 13 Apr 2010 15:33:05 +1000, Dave Airlie <airlied@gmail.com> wrote:
> On Tue, Apr 13, 2010 at 5:19 AM, Daniel Vetter <daniel@ffwll.ch> wrote:
> > On Mon, Apr 12, 2010 at 10:51:20AM -0700, Eric Anholt wrote:
> >> On Fri, 9 Apr 2010 21:05:03 +0200, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> >> > Daniel Vetter (6):
> >> > drm: extract drm_gem_object_init
> >> > drm: free core gem object from driver callbacks
> >> > drm/i915: introduce i915_gem_alloc_object
> >> > drm/i915: embed the gem object into drm_i915_gem_object
> >> > drm/i915: don't use ->driver_private anymore
> >> > drm/i915: drop pointer to drm_gem_object
> >>
> >> I like this series. Dave, should I pull this one?
> >
> > Cool. wrt merging I'd prefer if Dave could take the first two via drm-core.
> > That way round I could start working on the radeon/nouveau stuff
> > independently of the i915 stuff. That'd stall i915 slightly but i915 is the
> > easiest conversion (that's why I did it first) so I can quickly rebase in
> > case of conflicts
>
> I'll take these via my tree, Eric just let me know if I can assume your ack
> on the i915 ones and even the main one. I'll try and review them over the next
> couple of days.
OK. And if you felt like pulling my -next at the same time, that would
be awesome as then I can continue merging there based off of this
series.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 197 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:[~2010-04-13 23:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 19:05 [PATCH 0/6] make gem_object embedable and convert i915 driver Daniel Vetter
2010-04-09 19:05 ` [PATCH 1/6] drm: extract drm_gem_object_init Daniel Vetter
2010-04-09 19:05 ` [PATCH 2/6] drm: free core gem object from driver callbacks Daniel Vetter
2010-04-09 19:05 ` [PATCH 3/6] drm/i915: introduce i915_gem_alloc_object Daniel Vetter
2010-04-09 19:05 ` [PATCH 4/6] drm/i915: embed the gem object into drm_i915_gem_object Daniel Vetter
2010-04-09 19:05 ` [PATCH 5/6] drm/i915: don't use ->driver_private anymore Daniel Vetter
2010-04-09 19:05 ` [PATCH 6/6] drm/i915: drop pointer to drm_gem_object Daniel Vetter
2010-04-12 17:51 ` [PATCH 0/6] make gem_object embedable and convert i915 driver Eric Anholt
2010-04-12 19:19 ` Daniel Vetter
2010-04-13 5:33 ` Dave Airlie
2010-04-13 23:59 ` Eric Anholt [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=878w8qvr8z.fsf@pollan.anholt.net \
--to=eric@anholt.net \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.sourceforge.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;
as well as URLs for NNTP newsgroup(s).