From: Oscar Mateo <oscar.mateo@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/uc: Make intel_uc_prepare_fw() static
Date: Mon, 20 Mar 2017 10:17:48 -0700 [thread overview]
Message-ID: <ea8e7c8b-ee1d-c930-2ae8-5026ed1e149c@intel.com> (raw)
In-Reply-To: <20170315193819.155416-1-michal.wajdeczko@intel.com>
On 03/15/2017 12:38 PM, Michal Wajdeczko wrote:
> There is no need to expose this function as it is called from
> one function only. Also move it up to avoid forward declaration.
>
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> ---
> drivers/gpu/drm/i915/intel_uc.c | 269 ++++++++++++++++++++--------------------
> drivers/gpu/drm/i915/intel_uc.h | 2 -
> 2 files changed, 135 insertions(+), 136 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_uc.c b/drivers/gpu/drm/i915/intel_uc.c
> index 54c5aff..a0d8833 100644
> --- a/drivers/gpu/drm/i915/intel_uc.c
> +++ b/drivers/gpu/drm/i915/intel_uc.c
> @@ -86,6 +86,141 @@ void intel_uc_init_early(struct drm_i915_private *dev_priv)
> mutex_init(&dev_priv->guc.send_mutex);
> }
>
> +static void intel_uc_prepare_fw(struct drm_i915_private *dev_priv,
> + struct intel_uc_fw *uc_fw)
> +{
> + struct pci_dev *pdev = dev_priv->drm.pdev;
>
No need for prefix intel_*, since it's a static function?
-- Oscar
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-03-21 0:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 19:38 [PATCH] drm/i915/uc: Make intel_uc_prepare_fw() static Michal Wajdeczko
2017-03-15 19:55 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-03-20 10:01 ` [PATCH] " Joonas Lahtinen
2017-03-20 17:17 ` Oscar Mateo [this message]
2017-03-21 9:52 ` Joonas Lahtinen
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=ea8e7c8b-ee1d-c930-2ae8-5026ed1e149c@intel.com \
--to=oscar.mateo@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 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.