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 2/2] drm/i915: Make for_each_sprite() take dev_priv as argument
Date: Mon, 2 Mar 2015 19:01:52 +0100	[thread overview]
Message-ID: <20150302180152.GD18775@phenom.ffwll.local> (raw)
In-Reply-To: <1425135249-3225-3-git-send-email-damien.lespiau@intel.com>

On Sat, Feb 28, 2015 at 02:54:09PM +0000, Damien Lespiau wrote:
> Implicit usage of local variables in macros isn't exactly the greatest
> thing in the world, especially when that variable is the drm device and
> we want to move towards a broader use of the i915 device structure.
> 
> Let's make for_each_sprite() take dev_priv as its first argument then.
> 
> Suggested-by: Chris Wilson <chris@chris-wilson.co.uk>
> Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>

Queued for -next, thanks for the patch.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-03-02 18:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-28 14:54 [PATCH 0/2] Make for_each_{plane, sprite} take dev_priv as first argument Damien Lespiau
2015-02-28 14:54 ` [PATCH 1/2] drm/i915: Make for_each_plane() take dev_priv as argument Damien Lespiau
2015-02-28 21:04   ` Chris Wilson
2015-03-02 13:57     ` Damien Lespiau
2015-02-28 14:54 ` [PATCH 2/2] drm/i915: Make for_each_sprite() " Damien Lespiau
2015-03-02 18:01   ` Daniel Vetter [this message]
2015-03-03 11:42   ` shuang.he

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=20150302180152.GD18775@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