public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Dave Gordon <david.s.gordon@intel.com>
To: Jani Nikula <jani.nikula@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [RFC] Convert INTEL_INFO(...)->gen to INTEL_GEN(...)
Date: Mon, 11 Apr 2016 09:40:56 +0100	[thread overview]
Message-ID: <570B6318.3050005@intel.com> (raw)
In-Reply-To: <8737qwwls6.fsf@intel.com>

On 08/04/16 09:24, Jani Nikula wrote:
> On Thu, 07 Apr 2016, Dave Gordon <david.s.gordon@intel.com> wrote:
>> Since Jani has given us this macro, I thought I'd make use of it by
>> converting all existing instances of this construct with a really
>> simple little Coccinelle script:
>>
>> @intel_gen@
>>      expression E;
>> @@
>>      <...
>> -   INTEL_INFO(E)->gen
>> +   INTEL_GEN(E)
>>      ...>
>
> I intentionally did not do this because I think it causes more trouble
> than it's worth. Basically this will conflict with roughly all patches
> currently in flight. Yes, I admit I did tell people to go wild, but
> please let's do this piecemeal.
>
> BR,
> Jani.

The point of including the actual Cocci code in the commit message is 
that then anyone who has a set of not-yet-submitted changes can apply 
the Cocci script to their own codebase before attempting to rebase onto 
the new version of nightly, thus eliminating from the conflicts all 
those which are simply due to the patch applied to upstream.

For this reason, I'd like to recommend that anyone doing this sort of 
bulk transformation with Cocci or awk or just sed should /always/ 
include the transformation script.

As for doing it piecemeal, what are the chances that there will ever be 
a time when there are no changes in flight in, say, intel_display.c?

$ git churn drivers/gpu/drm/i915/*.c | tail -6

918	drivers/gpu/drm/i915/intel_ringbuffer.c
1027	drivers/gpu/drm/i915/intel_dp.c
1108	drivers/gpu/drm/i915/i915_irq.c
1448	drivers/gpu/drm/i915/intel_pm.c
1583	drivers/gpu/drm/i915/i915_gem.c
3290	drivers/gpu/drm/i915/intel_display.c

Perhaps the maintainers could target one file at a time, any time it 
looks like we're having a quiet period?

.Dave.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-04-11  8:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-07  9:48 [PATCH] drm/i915: add INTEL_GEN() helper shorthand for INTEL_INFO()->gen Jani Nikula
2016-04-07  9:52 ` Chris Wilson
2016-04-07 13:56   ` Jani Nikula
2016-04-07 16:22     ` [RFC] Convert INTEL_INFO(...)->gen to INTEL_GEN(...) Dave Gordon
2016-04-08  8:24       ` Jani Nikula
2016-04-11  8:40         ` Dave Gordon [this message]
2016-04-13 12:32     ` [PATCH] drm/i915: add INTEL_GEN() helper shorthand for INTEL_INFO()->gen Jani Nikula
2016-04-07 13:29 ` ✗ Fi.CI.BAT: failure for " Patchwork
2016-04-08  7:07 ` ✗ Fi.CI.BAT: failure for drm/i915: add INTEL_GEN() helper shorthand for INTEL_INFO()->gen (rev2) Patchwork

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=570B6318.3050005@intel.com \
    --to=david.s.gordon@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    /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