All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Arun Siluvery <arun.siluvery@linux.intel.com>,
	Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/5] intel_engine_cs renaming bomb
Date: Thu, 10 Mar 2016 16:47:00 +0000	[thread overview]
Message-ID: <56E1A504.2000600@linux.intel.com> (raw)
In-Reply-To: <56E1A43A.4040903@linux.intel.com>


On 10/03/16 16:43, Arun Siluvery wrote:
> On 10/03/2016 16:28, Tvrtko Ursulin wrote:
>>
>> Hi,
>>
>> On 10/03/16 15:00, Arun Siluvery wrote:
>>> On 10/03/2016 14:21, Tvrtko Ursulin wrote:
>>>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>>>
>>>> I think there is consesus to do this, but the question
>>>> is whether now is the time to do it?
>>>>
>>>> If desired, needs to go in quickly before it goes stale.
>>>>
>>>> But if not, it was an interesting exercise of learning
>>>> Coccinelle nevertheless.
>>>>
>>>> Tvrtko Ursulin (5):
>>>>    drm/i915: Rename local struct intel_engine_cs variables
>>>>    drm/i915: Rename intel_engine_cs function parameters
>>>>    drm/i915: Rename intel_engine_cs struct members
>>>>    drm/i915: More intel_engine_cs renaming
>>>>    drm/i915: More renaming of rings to engines
>>>>
>>>>   drivers/gpu/drm/i915/i915_cmd_parser.c       |  122 +--
>>>>   drivers/gpu/drm/i915/i915_debugfs.c          |  229 +++--
>>>>   drivers/gpu/drm/i915/i915_dma.c              |   12 +-
>>>>   drivers/gpu/drm/i915/i915_drv.h              |   70 +-
>>>>   drivers/gpu/drm/i915/i915_gem.c              |  316 +++---
>>>>   drivers/gpu/drm/i915/i915_gem_context.c      |  168 +--
>>>>   drivers/gpu/drm/i915/i915_gem_debug.c        |   15 +-
>>>>   drivers/gpu/drm/i915/i915_gem_execbuffer.c   |  120 +--
>>>>   drivers/gpu/drm/i915/i915_gem_gtt.c          |   94 +-
>>>>   drivers/gpu/drm/i915/i915_gem_render_state.c |   12 +-
>>>>   drivers/gpu/drm/i915/i915_gem_render_state.h |    2 +-
>>>>   drivers/gpu/drm/i915/i915_gpu_error.c        |  158 +--
>>>>   drivers/gpu/drm/i915/i915_guc_submission.c   |   37 +-
>>>>   drivers/gpu/drm/i915/i915_irq.c              |  243 ++---
>>>>   drivers/gpu/drm/i915/i915_trace.h            |    6 +-
>>>>   drivers/gpu/drm/i915/intel_display.c         |  114 +--
>>>>   drivers/gpu/drm/i915/intel_guc_loader.c      |   12 +-
>>>>   drivers/gpu/drm/i915/intel_lrc.c             |  826 ++++++++-------
>>>>   drivers/gpu/drm/i915/intel_lrc.h             |   16 +-
>>>>   drivers/gpu/drm/i915/intel_mocs.c            |    6 +-
>>>>   drivers/gpu/drm/i915/intel_overlay.c         |   60 +-
>>>>   drivers/gpu/drm/i915/intel_pm.c              |   38 +-
>>>>   drivers/gpu/drm/i915/intel_ringbuffer.c      | 1425
>>>> +++++++++++++-------------
>>>>   drivers/gpu/drm/i915/intel_ringbuffer.h      |   86 +-
>>>>   drivers/gpu/drm/i915/intel_uncore.c          |    4 +-
>>>>   25 files changed, 2132 insertions(+), 2059 deletions(-)
>>>>
>>>
>>> Are the filenames also going to be renamed?
>>
>> I can't spot any files to rename, which ones you had in mind?
>
> I mean intel_ringbuffer.c -> intel_engine.c ? or may not be necessary.

I would leave it since everyone calls the it legacy ringbuffer 
submission, so it makes sense for it to implemented in an adequately 
named file.

In fact I have second thoughts on a couple renames I did in 5/5, should 
probably undo them.

Regards,

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

  reply	other threads:[~2016-03-10 16:47 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-10 14:21 [PATCH 0/5] intel_engine_cs renaming bomb Tvrtko Ursulin
2016-03-10 14:21 ` [PATCH 1/5] drm/i915: Rename local struct intel_engine_cs variables Tvrtko Ursulin
2016-03-10 14:21 ` [PATCH 2/5] drm/i915: Rename intel_engine_cs function parameters Tvrtko Ursulin
2016-03-10 15:33   ` kbuild test robot
2016-03-10 14:21 ` [PATCH 3/5] drm/i915: Rename intel_engine_cs struct members Tvrtko Ursulin
2016-03-10 15:18   ` kbuild test robot
2016-03-10 15:47   ` [PATCH 3/5 v2] " Tvrtko Ursulin
2016-03-10 14:21 ` [PATCH 4/5] drm/i915: More intel_engine_cs renaming Tvrtko Ursulin
2016-03-10 15:47   ` [PATCH 4/5 v2] " Tvrtko Ursulin
2016-03-10 14:21 ` [PATCH 5/5] drm/i915: More renaming of rings to engines Tvrtko Ursulin
2016-03-10 14:49   ` Chris Wilson
2016-03-10 14:59     ` Tvrtko Ursulin
2016-03-11 11:38   ` [PATCH v2 " Tvrtko Ursulin
2016-03-11 13:19   ` [PATCH 5/5 v3] " Tvrtko Ursulin
2016-03-10 14:52 ` [PATCH 0/5] intel_engine_cs renaming bomb Chris Wilson
2016-03-10 15:00 ` Arun Siluvery
2016-03-10 16:28   ` Tvrtko Ursulin
2016-03-10 16:43     ` Arun Siluvery
2016-03-10 16:47       ` Tvrtko Ursulin [this message]
2016-03-10 15:10 ` ✗ Fi.CI.BAT: failure for " Patchwork
2016-03-10 16:30 ` ✗ Fi.CI.BAT: warning for intel_engine_cs renaming bomb (rev3) Patchwork
2016-03-11  9:49   ` Tvrtko Ursulin
2016-03-11  9:52     ` Arun Siluvery
2016-03-11 12:30 ` ✗ Fi.CI.BAT: warning for intel_engine_cs renaming bomb (rev4) Patchwork
2016-03-11 14:32 ` ✗ Fi.CI.BAT: failure for intel_engine_cs renaming bomb (rev5) 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=56E1A504.2000600@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=arun.siluvery@linux.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 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.