From: Daniel Vetter <daniel@ffwll.ch>
To: sedat.dilek@gmail.com
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 19:14:43 +0100 [thread overview]
Message-ID: <20101114181443.GC4497@viiv.ffwll.ch> (raw)
In-Reply-To: <AANLkTimUqcDN-HEOKL+v=C5Uv9Yh=4ZTkHf9=y0oPHLv@mail.gmail.com>
On Sun, Nov 14, 2010 at 06:52:35PM +0100, Sedat Dilek wrote:
> NOPE, linux-next is up-to-date what drm-next concerns.
Sorry for wasting your time, I've totally forgotten about a patch in
drm-intel-next
(git://git.kernel.org/pub/scm/linux/kernel/git/ickle/drm-intel.git),
namely:
commit d935cc61d466f6cc7514032835f4fc379cb7e2ca
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date: Thu Sep 16 15:13:11 2010 +0200
drm_mm: add support for range-restricted fair-lru scans
That one's necessary, too.
Yours, Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2010-11-14 18:11 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
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 [this message]
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=20101114181443.GC4497@viiv.ffwll.ch \
--to=daniel@ffwll.ch \
--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).