From: Andrew Morton <akpm@linux-foundation.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
Rik van Riel <riel@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Michel Lespinasse <walken@google.com>
Subject: Re: [PATCH] lib: Export interval_tree
Date: Mon, 27 Jan 2014 15:13:50 -0800 [thread overview]
Message-ID: <20140127151350.e44323b007f00229ac831a90@linux-foundation.org> (raw)
In-Reply-To: <1390739073-4519-1-git-send-email-chris@chris-wilson.co.uk>
On Sun, 26 Jan 2014 12:24:33 +0000 Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Note for maintainers, this is being proposed for use by i915.ko, so it
> may make the most sense to merge it via the drm/i915 tree in the next
> cycle.
Yes, please proceed that way.
prev parent reply other threads:[~2014-01-27 23:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 15:07 [PATCH 1/3] lib: Always build and export interval_tree Chris Wilson
2014-01-21 15:07 ` [PATCH 2/3] drm/i915: Do not call retire_requests from wait_for_rendering Chris Wilson
2014-01-21 15:07 ` [PATCH 3/3] drm/i915: Introduce mapping of user pages into video memory (userptr) ioctl Chris Wilson
2014-01-22 9:46 ` [PATCH] " Chris Wilson
2014-01-24 9:00 ` Chris Wilson
2014-01-27 17:56 ` Volkin, Bradley D
2014-01-27 18:09 ` Chris Wilson
2014-01-25 4:42 ` [PATCH 1/3] lib: Always build and export interval_tree Michel Lespinasse
2014-01-26 11:27 ` Chris Wilson
2014-01-26 11:58 ` Michel Lespinasse
2014-01-26 12:25 ` Chris Wilson
2014-01-26 12:24 ` [PATCH] lib: Export interval_tree Chris Wilson
2014-01-26 12:34 ` Michel Lespinasse
2014-01-26 13:54 ` Daniel Vetter
2014-01-26 14:03 ` [Intel-gfx] " Michel Lespinasse
2014-01-27 23:13 ` Andrew Morton [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=20140127151350.e44323b007f00229ac831a90@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.p.zijlstra@chello.nl \
--cc=aarcange@redhat.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
--cc=walken@google.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