From: Damien Lespiau <damien.lespiau@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 0/5] Make num_sprites a per pipe value (v3)
Date: Mon, 3 Mar 2014 17:31:43 +0000 [thread overview]
Message-ID: <1393867908-4604-1-git-send-email-damien.lespiau@intel.com> (raw)
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
--
Damien
Damien Lespiau (5):
drm/i915: Use a pipe variable to cycle through the pipes
drm/i915: Don't declare unnecessary shadowing variable
drm/i915: Replace a few for_each_pipe(i) by for_each_pipe(pipe)
drm/i915: Add a for_each_sprite() macro
drm/i915: Make num_sprites a per-pipe value
drivers/gpu/drm/i915/i915_debugfs.c | 15 +++++++--------
drivers/gpu/drm/i915/i915_dma.c | 8 ++++++--
drivers/gpu/drm/i915/i915_drv.h | 5 +++--
drivers/gpu/drm/i915/i915_irq.c | 14 +++++++-------
drivers/gpu/drm/i915/intel_display.c | 21 +++++++++++----------
drivers/gpu/drm/i915/intel_pm.c | 16 ++++++++--------
6 files changed, 42 insertions(+), 37 deletions(-)
--
1.8.3.1
next reply other threads:[~2014-03-03 17:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 17:31 Damien Lespiau [this message]
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
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=1393867908-4604-1-git-send-email-damien.lespiau@intel.com \
--to=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