public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Damien Lespiau <damien.lespiau@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/4] for_each_{intel_,}crtc v2
Date: Wed, 14 May 2014 00:40:03 +0200	[thread overview]
Message-ID: <20140513224003.GZ3908@phenom.ffwll.local> (raw)
In-Reply-To: <1400020344-17248-1-git-send-email-damien.lespiau@intel.com>

On Tue, May 13, 2014 at 11:32:20PM +0100, Damien Lespiau wrote:
> With Daniel's help to figure out an arcane corner of coccinelle, here is v2 of
> a series introducing macros to iterate through the CRTCs instead of using
> list_for_each_entry() and mode_config.crtc_list, a tiny bit more readable and
> easier to recall.
> 
> Damien Lespiau (4):
>   drm/i915: Introduce a for_each_intel_crtc() macro
>   drm/i915: Use for_each_intel_crtc() when iterating through intel_crtcs
>   drm/i915: Introduce a for_each_crtc() macro
>   drm/i915: Use for_each_crtc() when iterating through the CRTCs

Thanks, all four pulled into dinq.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

      parent reply	other threads:[~2014-05-13 22:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13 22:32 [PATCH 0/4] for_each_{intel_,}crtc v2 Damien Lespiau
2014-05-13 22:32 ` [PATCH 1/4] drm/i915: Introduce a for_each_intel_crtc() macro Damien Lespiau
2014-05-13 22:32 ` [PATCH 2/4] drm/i915: Use for_each_intel_crtc() when iterating through intel_crtcs Damien Lespiau
2014-05-13 22:32 ` [PATCH 3/4] drm/i915: Introduce a for_each_crtc() macro Damien Lespiau
2014-05-14  8:56   ` Jani Nikula
2014-05-13 22:32 ` [PATCH 4/4] drm/i915: Use for_each_crtc() when iterating through the CRTCs Damien Lespiau
2014-05-13 22:40 ` 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=20140513224003.GZ3908@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --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