From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Sagar Arun Kamble <sagar.a.kamble@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: "Nikula, Jani" <jani.nikula@intel.com>
Subject: Re: [PATCH 1/1] drm/i915/guc: Update header guard name of intel_guc_submission.h
Date: Fri, 24 Nov 2017 13:15:46 +0200 [thread overview]
Message-ID: <1511522146.3566.12.camel@linux.intel.com> (raw)
In-Reply-To: <1511511650-13756-1-git-send-email-sagar.a.kamble@intel.com>
On Fri, 2017-11-24 at 13:50 +0530, Sagar Arun Kamble wrote:
> While renaming i915_guc_submission.h to intel_guc_submission.h, update of
> header guard name to _INTEL_GUC_SUBMISSION_H_ was missed.
>
> Fixes: a269574489d4 (drm/i915/guc: Rename i915_guc_submission.c|h to intel_guc_submission.c|h)
+ Jani
There was lately a request from Jani to not to include "Fixes:" for
purely stylistical fixes. So if there's no actual functional impact, no
"Fixes:".
I'm still unsure if we have alternative markup agreed upon?
Regards, Joonas
> Signed-off-by: Sagar Arun Kamble <sagar.a.kamble@intel.com>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> ---
> drivers/gpu/drm/i915/intel_guc_submission.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_guc_submission.h b/drivers/gpu/drm/i915/intel_guc_submission.h
> index e901192..021fe85 100644
> --- a/drivers/gpu/drm/i915/intel_guc_submission.h
> +++ b/drivers/gpu/drm/i915/intel_guc_submission.h
> @@ -22,8 +22,8 @@
> *
> */
>
> -#ifndef _I915_GUC_SUBMISSION_H_
> -#define _I915_GUC_SUBMISSION_H_
> +#ifndef _INTEL_GUC_SUBMISSION_H_
> +#define _INTEL_GUC_SUBMISSION_H_
>
> #include <linux/spinlock.h>
>
--
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
next prev parent reply other threads:[~2017-11-24 11:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 8:20 [PATCH 1/1] drm/i915/guc: Update header guard name of intel_guc_submission.h Sagar Arun Kamble
2017-11-24 9:04 ` ✓ Fi.CI.BAT: success for series starting with [1/1] " Patchwork
2017-11-24 9:32 ` [PATCH 1/1] " Michal Wajdeczko
2017-11-24 9:42 ` Chris Wilson
2017-11-24 12:42 ` Sagar Arun Kamble
2017-11-24 10:18 ` ✓ Fi.CI.IGT: success for series starting with [1/1] " Patchwork
2017-11-24 10:37 ` Chris Wilson
2017-11-24 11:15 ` Joonas Lahtinen [this message]
2017-11-24 12:43 ` [PATCH 1/1] " Sagar Arun Kamble
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=1511522146.3566.12.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=sagar.a.kamble@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.