From: Daniel Vetter <daniel@ffwll.ch>
To: Imre Deak <imre.deak@intel.com>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Tejun Heo <tj@kernel.org>, Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH 0/2] lib/scatterlist: sg_page_iter: support for memory w/o backing pages
Date: Tue, 26 Mar 2013 15:50:20 +0100 [thread overview]
Message-ID: <20130326145020.GT9021@phenom.ffwll.local> (raw)
In-Reply-To: <1364303659-1951-1-git-send-email-imre.deak@intel.com>
On Tue, Mar 26, 2013 at 03:14:17PM +0200, Imre Deak wrote:
> When adding sg_page_iter I haven't thought properly through the use case
> for sg lists w/o backing pages - which is specific to the i915 driver -
> so this patchset adds support for this.
>
> It applies on the i915 tree [1], where the iterator is in use already.
>
> [1] git://people.freedesktop.org/~danvet/drm-intel [nightly branch]
i915 patches are already included in linux-next, so should apply on top of
that, too. So can this go in through -mm for 3.10 or should I slurp it in
through drm-intel trees (once it passes review)? I'd like to ditch the
dummy page hack we're currently using (i.e. patch 2).
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2013-03-26 14:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 13:14 Imre Deak
2013-03-26 13:14 ` [PATCH 1/2] lib/scatterlist: sg_page_iter: support sg lists " Imre Deak
2013-03-26 13:14 ` [PATCH 2/2] Revert "drm/i915: set dummy page for stolen objects" Imre Deak
2013-03-26 14:50 ` Daniel Vetter [this message]
2013-03-26 19:57 ` [PATCH 0/2] lib/scatterlist: sg_page_iter: support for memory w/o backing pages Andrew Morton
2013-03-27 0:21 ` Daniel Vetter
2013-03-26 22:50 ` [Intel-gfx] " Damien Lespiau
2013-03-27 0:20 ` 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=20130326145020.GT9021@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=akpm@linux-foundation.org \
--cc=daniel.vetter@ffwll.ch \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.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
all inboxes | Powered by JetHome®