dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@googlemail.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: daniel.vetter@ffwll.ch, DRI <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 0/9] make struct drm_mm_node embeddable
Date: Sun, 14 Nov 2010 16:52:43 +0100	[thread overview]
Message-ID: <AANLkTikbS0=zARPm+RaXz_FUVDBb-183+mfJygoWv5Ef@mail.gmail.com> (raw)
In-Reply-To: <0d30dc$k5v4jf@orsmga001.jf.intel.com>

On Sun, Nov 14, 2010 at 3:38 PM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Sun, 14 Nov 2010 15:03:31 +0100, Sedat Dilek <sedat.dilek@googlemail.com> wrote:
>> [ Please CC me I am not subscribed to dri-devel ML ]
>>
>> [ QUOTE ]
>> As a proof of concept I've converted i915. Beware though, the drm/i915
>> patches depend on my direct-gtt patches (which are actually the reason for
>> this series here).
>>
>> [ /QUOTE ]
>>
>> Against which GIT tree or linux-next version are these patchset for?
>
> git://anongit.freedesktop.org/~danvet/drm direct-gtt
> -Chris
>
> --
> Chris Wilson, Intel Open Source Technology Centre
>

Thank you for the pointer to the right GIT repository and branch.
Looks like [1] has Daniel's patchset (9 patches) already included.

To attract more people for testing or joining it would be appreciated
these interesting work would be (re)based on Dave's drm-next GIT tree,
as this one is going to linux-next.

Or is drm-next/linux-next work for intel-gfxcards done elsewhere?

Pulling/Merging Daniel's GIT branch into drm-next (or linux-next) or
Linus-tree is causing conflicts.

- Sedat -

[1] http://cgit.freedesktop.org/~danvet/drm/log/?h=embed-gtt-space

  reply	other threads:[~2010-11-14 15:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-14 14:03 [PATCH 0/9] make struct drm_mm_node embeddable Sedat Dilek
2010-11-14 14:38 ` Chris Wilson
2010-11-14 15:52   ` Sedat Dilek [this message]
2010-11-14 16:13     ` Daniel Vetter
2010-11-14 16:56       ` Sedat Dilek
2010-11-14 17:14         ` Daniel Vetter
2010-11-14 17:27           ` Sedat Dilek
2010-11-14 17:52             ` Sedat Dilek
2010-11-14 18:14               ` Daniel Vetter
2010-11-14 18:19                 ` Sedat Dilek
2010-11-14 18:31                 ` Sedat Dilek
2010-11-14 18:54                   ` Daniel Vetter
2010-11-14 19:55                     ` Sedat Dilek
  -- strict thread matches above, loose matches on Subject: below --
2010-11-15 10:31 Sedat Dilek
2010-11-12 17:36 Daniel Vetter
2010-11-12 17:56 ` Chris Wilson
2010-11-15  7:58 ` Thomas Hellstrom
2010-11-15 19:45   ` Daniel Vetter
2010-11-15 20:40     ` Thomas Hellstrom
2010-11-15 20:54       ` Daniel Vetter

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='AANLkTikbS0=zARPm+RaXz_FUVDBb-183+mfJygoWv5Ef@mail.gmail.com' \
    --to=sedat.dilek@googlemail.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=sedat.dilek@gmail.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 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).