From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Damien Lespiau <damien.lespiau@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/5] Make num_sprites a per pipe value (v3)
Date: Wed, 5 Mar 2014 18:48:38 +0100 [thread overview]
Message-ID: <20140305174838.GQ17001@phenom.ffwll.local> (raw)
In-Reply-To: <20140303211638.GB17720@nuc-i3427.alporthouse.com>
On Mon, Mar 03, 2014 at 09:16:38PM +0000, Chris Wilson wrote:
> On Mon, Mar 03, 2014 at 05:31:43PM +0000, Damien Lespiau wrote:
> > Follow up of:
> > http://lists.freedesktop.org/archives/intel-gfx/2014-February/040789.html
> >
> > With a couple of changes:
> >
> > - Fix up the poor style when initializing the per-pipe num_sprites
> > - Added more for_each_pipe(pipe) conversion
> > - Added a small cleanup patch spotted when doing the previous patch
>
> Nothing upset me (apart from the concept of variable number of planes
> per pipe and the inflexible assumption that it is constant in certain
> client facing APIs), not even the expansion of intel_info, so
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
All pulled in, thanks for patches&review.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
prev parent reply other threads:[~2014-03-05 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 17:31 [PATCH 0/5] Make num_sprites a per pipe value (v3) Damien Lespiau
2014-03-03 17:31 ` [PATCH 1/5] drm/i915: Use a pipe variable to cycle through the pipes Damien Lespiau
2014-03-03 17:31 ` [PATCH 2/5] drm/i915: Don't declare unnecessary shadowing variable Damien Lespiau
2014-03-03 17:31 ` [PATCH 3/5] drm/i915: Replace a few for_each_pipe(i) by for_each_pipe(pipe) Damien Lespiau
2014-03-03 17:31 ` [PATCH 4/5] drm/i915: Add a for_each_sprite() macro Damien Lespiau
2014-03-03 17:31 ` [PATCH 5/5] drm/i915: Make num_sprites a per-pipe value Damien Lespiau
2014-03-03 21:16 ` [PATCH 0/5] Make num_sprites a per pipe value (v3) Chris Wilson
2014-03-05 17:48 ` Daniel Vetter [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=20140305174838.GQ17001@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--cc=damien.lespiau@intel.com \
--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