From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe/guc: Fix include guard for SR-IOV ABI
Date: Tue, 13 Feb 2024 17:21:46 -0500 [thread overview]
Message-ID: <ZcvreuJR1TjPs1_t@intel.com> (raw)
In-Reply-To: <20240213214908.1481-1-michal.wajdeczko@intel.com>
On Tue, Feb 13, 2024 at 10:49:08PM +0100, Michal Wajdeczko wrote:
> Use include guard macro name that follows naming used by the other
> GuC ABI files.
>
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
hmmm, I believe the ABI prefix should be avoided, but anyway
you are right. this is how the rest of the headers there are,
so,
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> drivers/gpu/drm/xe/abi/guc_actions_sriov_abi.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/abi/guc_actions_sriov_abi.h b/drivers/gpu/drm/xe/abi/guc_actions_sriov_abi.h
> index 5496a5890847..fe7a93ce3aa5 100644
> --- a/drivers/gpu/drm/xe/abi/guc_actions_sriov_abi.h
> +++ b/drivers/gpu/drm/xe/abi/guc_actions_sriov_abi.h
> @@ -3,8 +3,8 @@
> * Copyright © 2023 Intel Corporation
> */
>
> -#ifndef _GUC_ACTIONS_PF_ABI_H
> -#define _GUC_ACTIONS_PF_ABI_H
> +#ifndef _ABI_GUC_ACTIONS_SRIOV_ABI_H
> +#define _ABI_GUC_ACTIONS_SRIOV_ABI_H
>
> #include "guc_communication_ctb_abi.h"
>
> --
> 2.43.0
>
next prev parent reply other threads:[~2024-02-13 22:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 21:49 [PATCH] drm/xe/guc: Fix include guard for SR-IOV ABI Michal Wajdeczko
2024-02-13 22:21 ` Rodrigo Vivi [this message]
2024-02-13 23:39 ` ✓ CI.Patch_applied: success for " Patchwork
2024-02-13 23:40 ` ✓ CI.checkpatch: " Patchwork
2024-02-13 23:40 ` ✓ CI.KUnit: " Patchwork
2024-02-13 23:51 ` ✓ CI.Build: " Patchwork
2024-02-13 23:51 ` ✓ CI.Hooks: " Patchwork
2024-02-13 23:53 ` ✓ CI.checksparse: " Patchwork
2024-02-14 0:15 ` ✓ CI.BAT: " 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=ZcvreuJR1TjPs1_t@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-xe@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.