From: Nirmoy Das <nirmoy.das@linux.intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/xe/guc: Drop unused legacy GuC message ABI definitions
Date: Mon, 10 Jun 2024 15:02:12 +0200 [thread overview]
Message-ID: <ceb49b55-9bbf-45b3-ab0e-b79c928587b9@linux.intel.com> (raw)
In-Reply-To: <20240610120411.1768-2-michal.wajdeczko@intel.com>
On 6/10/2024 2:04 PM, Michal Wajdeczko wrote:
> Those were copy-pasted from i915 code and never used in Xe driver.
>
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
Reviewed-by: Nirmoy Das <nirmoy.das@intel.com>
> ---
> drivers/gpu/drm/xe/abi/guc_messages_abi.h | 13 -------------
> 1 file changed, 13 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/abi/guc_messages_abi.h b/drivers/gpu/drm/xe/abi/guc_messages_abi.h
> index 534a39db7772..e32142e3fe41 100644
> --- a/drivers/gpu/drm/xe/abi/guc_messages_abi.h
> +++ b/drivers/gpu/drm/xe/abi/guc_messages_abi.h
> @@ -220,17 +220,4 @@
> #define GUC_HXG_RESPONSE_MSG_0_DATA0 GUC_HXG_MSG_0_AUX
> #define GUC_HXG_RESPONSE_MSG_n_DATAn GUC_HXG_MSG_n_PAYLOAD
>
> -/* deprecated */
> -#define INTEL_GUC_MSG_TYPE_SHIFT 28
> -#define INTEL_GUC_MSG_TYPE_MASK (0xF << INTEL_GUC_MSG_TYPE_SHIFT)
> -#define INTEL_GUC_MSG_DATA_SHIFT 16
> -#define INTEL_GUC_MSG_DATA_MASK (0xFFF << INTEL_GUC_MSG_DATA_SHIFT)
> -#define INTEL_GUC_MSG_CODE_SHIFT 0
> -#define INTEL_GUC_MSG_CODE_MASK (0xFFFF << INTEL_GUC_MSG_CODE_SHIFT)
> -
> -enum intel_guc_msg_type {
> - INTEL_GUC_MSG_TYPE_REQUEST = 0x0,
> - INTEL_GUC_MSG_TYPE_RESPONSE = 0xF,
> -};
> -
> #endif
next prev parent reply other threads:[~2024-06-10 13:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 12:04 [PATCH 0/2] Fixup GuC ABI Michal Wajdeczko
2024-06-10 12:04 ` [PATCH 1/2] drm/xe/guc: Drop unused legacy GuC message ABI definitions Michal Wajdeczko
2024-06-10 13:02 ` Nirmoy Das [this message]
2024-06-10 12:04 ` [PATCH 2/2] drm/xe/guc: Add kernel-doc for HXG Fast Request Michal Wajdeczko
2024-06-10 13:05 ` Nirmoy Das
2024-06-11 15:09 ` Lucas De Marchi
2024-06-11 16:18 ` Michal Wajdeczko
2024-06-10 12:11 ` ✓ CI.Patch_applied: success for Fixup GuC ABI Patchwork
2024-06-10 12:11 ` ✓ CI.checkpatch: " Patchwork
2024-06-10 12:12 ` ✓ CI.KUnit: " Patchwork
2024-06-10 12:28 ` ✓ CI.Build: " Patchwork
2024-06-10 12:30 ` ✓ CI.Hooks: " Patchwork
2024-06-10 12:31 ` ✓ CI.checksparse: " Patchwork
2024-06-10 13:26 ` ✓ CI.BAT: " Patchwork
2024-06-10 15:12 ` ✗ CI.FULL: failure " Patchwork
2024-06-10 16:55 ` Michal Wajdeczko
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=ceb49b55-9bbf-45b3-ab0e-b79c928587b9@linux.intel.com \
--to=nirmoy.das@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox