From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Fix inconsistent naming of i915_guc_client parameter
Date: Fri, 16 Dec 2016 10:02:32 +0200 [thread overview]
Message-ID: <1481875352.3134.0.camel@linux.intel.com> (raw)
In-Reply-To: <20161215195321.63804-1-michal.wajdeczko@intel.com>
On to, 2016-12-15 at 19:53 +0000, Michal Wajdeczko wrote:
> We usually use 'client' as identifier for the i915_guc_client.
> For unknown reason, few functions were using 'gc' name.
>
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
Looks good, I'll merge this.
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
prev parent reply other threads:[~2016-12-16 8:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 19:53 [PATCH] drm/i915: Fix inconsistent naming of i915_guc_client parameter Michal Wajdeczko
2016-12-15 20:23 ` ✓ Fi.CI.BAT: success for " Patchwork
2016-12-16 8:02 ` Joonas Lahtinen [this message]
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=1481875352.3134.0.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michal.wajdeczko@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