public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Arkadiusz Hiler <arkadiusz.hiler@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/5] drm/i915/uc: Rename intel_?uc_{setup, load}() to _init_hw()
Date: Wed, 15 Feb 2017 14:41:40 +0200	[thread overview]
Message-ID: <1487162500.8490.19.camel@linux.intel.com> (raw)
In-Reply-To: <20170214161541.26781-2-arkadiusz.hiler@intel.com>

On ti, 2017-02-14 at 17:15 +0100, Arkadiusz Hiler wrote:
> GuC historically has two "startup" functions called _init() and _setup()
> 
> Then HuC came with it's _init() and _load().
> 
> To make naming more consistent this commit renames intel_guc_setup() and
> intel_huc_load() to *uc_init_hw() as it it seams more fitting - they are
> called from the i915_gem_init_hw().
> 
> Cc: Anusha Srivatsa <anusha.srivatsa@intel.com>
> Cc: Michal Winiarski <michal.winiarski@intel.com>
> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Signed-off-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>

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

Regards, Joonas
-- 
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2017-02-15 12:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-14 16:15 [PATCH v2 0/5] GuC Scrub vol. 1 Arkadiusz Hiler
2017-02-14 16:15 ` [PATCH 1/5] drm/i915/uc: Rename intel_?uc_{setup, load}() to _init_hw() Arkadiusz Hiler
2017-02-14 19:14   ` Michal Wajdeczko
2017-02-14 21:58   ` Chris Wilson
2017-02-15 12:41   ` Joonas Lahtinen [this message]
2017-02-14 16:15 ` [PATCH 2/5] drm/i915/uc: Introduce intel_uc_init() Arkadiusz Hiler
2017-02-14 16:15 ` [PATCH 3/5] drm/i915/guc: Extract param logic form guc_init Arkadiusz Hiler
2017-02-14 19:37   ` Michal Wajdeczko
2017-02-15 12:48     ` Joonas Lahtinen
2017-02-15 15:10       ` Arkadiusz Hiler
2017-02-14 16:15 ` [PATCH 4/5] drm/i915/guc: Simplify intel_guc_init_hw() Arkadiusz Hiler
2017-02-14 20:07   ` Michal Wajdeczko
2017-02-14 16:15 ` [PATCH 5/5] drm/i915/uc: Simplify fw_path Arkadiusz Hiler
2017-02-14 20:23   ` Michal Wajdeczko
2017-02-15 14:12     ` Arkadiusz Hiler
2017-02-14 20:52 ` ✓ Fi.CI.BAT: success for GuC Scrub vol. 1 (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=1487162500.8490.19.camel@linux.intel.com \
    --to=joonas.lahtinen@linux.intel.com \
    --cc=arkadiusz.hiler@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