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] drm/i915: Use dev_priv as first argument of for_each_pipe()
Date: Tue, 26 Aug 2014 09:40:29 +0200 [thread overview]
Message-ID: <20140826074029.GZ15520@phenom.ffwll.local> (raw)
In-Reply-To: <20140818131306.GJ16480@nuc-i3427.alporthouse.com>
On Mon, Aug 18, 2014 at 02:13:06PM +0100, Chris Wilson wrote:
> On Mon, Aug 18, 2014 at 02:07:40PM +0100, Damien Lespiau wrote:
> > On Mon, Aug 18, 2014 at 01:58:06PM +0100, Chris Wilson wrote:
> > > On Mon, Aug 18, 2014 at 01:49:10PM +0100, Damien Lespiau wrote:
> > > > Chris has decided that enough is enough. It's time to fixup dev Vs
> > > > dev_priv. This is a modest contribution to the crusade.
> > > >
> > > > v2: Still use INTEL_INFO(), for the (mythical!) case we want to hardcode
> > > > the info struct with defines (Chris)
> > > > Rename the macro argument from 'dev' to 'dev_priv' (Jani)
> > > >
> > > > v3: Use names unlikely to be used as macro arguments (Chris)
> > >
> > > I can be annoying! These macros typically take the iter as the first
> > > argument...
> >
> > How typical is your typical?
>
> list_for_each and everything derived from them that paid attention...
>
> > #define for_each_pipe(__dev_priv, __p)
> > #define for_each_crtc(dev, crtc)
> > #define for_each_intel_crtc(dev, intel_crtc)
> > #define for_each_intel_encoder(dev, intel_encoder)
> > #define for_each_encoder_on_crtc(dev, __crtc, intel_encoder)
> > #define for_each_connector_on_encoder(dev, __encoder, intel_connector)
> >
> > Sounds like a lot of churn for no good reason this time.
>
> Or that I forgot to tell you about this detail last time.
I think a lot of those are on me ;-) Patch merged to dinq, thanks.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-08-26 7:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 17:34 [PATCH] drm/i915: Use dev_priv as first argument of for_each_pipe() Damien Lespiau
2014-08-15 18:15 ` Chris Wilson
2014-08-18 10:00 ` Damien Lespiau
2014-08-18 10:07 ` Chris Wilson
2014-08-18 12:49 ` Damien Lespiau
2014-08-18 12:58 ` Chris Wilson
2014-08-18 13:07 ` Damien Lespiau
2014-08-18 13:13 ` Chris Wilson
2014-08-26 7:40 ` Daniel Vetter [this message]
2014-08-18 8:04 ` Jani Nikula
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=20140826074029.GZ15520@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.