All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Rename drm_i915_gem_request to i915_request
Date: Wed, 21 Feb 2018 20:40:51 +0200	[thread overview]
Message-ID: <151923845145.9037.8159725745344159628@jlahtine-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20180221095636.6649-1-chris@chris-wilson.co.uk>

Quoting Chris Wilson (2018-02-21 11:56:36)
> We want to de-emphasize the link between the request (dependency,
> execution and fence tracking) from GEM and so rename the struct from
> drm_i915_gem_request to i915_request. That is we may implement the GEM
> user interface on top of requests, but they are an abstraction for
> tracking execution rather than an implementation detail of GEM. (Since
> they are not tied to HW, we keep the i915 prefix as opposed to intel.)
> 
> In short, the spatch:
> @@
> 
> @@
> - struct drm_i915_gem_request
> + struct i915_request
> 
> A corollary to contracting the type name, we also harmonise on using
> 'rq' shorthand for local variables where space if of the essence and
> repetition makes 'request' unwieldy. For globals and struct members,
> 'request' is still much preferred for its clarity.
> 
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Cc: Michał Winiarski <michal.winiarski@intel.com>
> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>

Right, should not cause a mayhem when merged now.

Acked-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>

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

  parent reply	other threads:[~2018-02-21 18:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-21  9:56 [PATCH] drm/i915: Rename drm_i915_gem_request to i915_request Chris Wilson
2018-02-21 10:19 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Rename drm_i915_gem_request to i915_request (rev2) Patchwork
2018-02-21 10:19 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-02-21 10:33 ` ✓ Fi.CI.BAT: success " Patchwork
2018-02-21 11:55 ` ✓ Fi.CI.IGT: " Patchwork
2018-02-21 12:05 ` [PATCH] drm/i915: Rename drm_i915_gem_request to i915_request Mika Kuoppala
2018-02-21 12:54 ` Michał Winiarski
2018-02-21 18:40 ` Joonas Lahtinen [this message]
2018-02-21 21:31   ` Chris Wilson
  -- strict thread matches above, loose matches on Subject: below --
2018-02-08 23:11 Chris Wilson
2018-02-09  7:48 ` Joonas Lahtinen
2018-02-09  9:32   ` Chris Wilson
2018-02-09 10:15     ` Mika Kuoppala

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=151923845145.9037.8159725745344159628@jlahtine-desk.ger.corp.intel.com \
    --to=joonas.lahtinen@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --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.