intel-xe.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Maarten Lankhorst <dev@lankhorst.se>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
	intel-xe@lists.freedesktop.org
Subject: Re: [PATCH] drm/xe: Drop unused ggtt_balloon field
Date: Mon, 11 May 2026 08:58:37 +0200	[thread overview]
Message-ID: <56f80dfc-4a87-4423-8ce1-e94e6c60ace6@lankhorst.se> (raw)
In-Reply-To: <20260510205605.642-1-michal.wajdeczko@intel.com>

Hey,

Den 2026-05-10 kl. 22:56, skrev Michal Wajdeczko:
> During recent GGTT refactoring we missed to drop now unused field
> from the xe_tile. Drop it now.
> 
> Fixes: e904c56ba6e0 ("drm/xe: Rewrite GGTT VF initialization")
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> ---
> Cc: Maarten Lankhorst <dev@lankhorst.se>
> ---
>  drivers/gpu/drm/xe/xe_tile_types.h | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_tile_types.h b/drivers/gpu/drm/xe/xe_tile_types.h
> index 33932fd547d7..0048100ccb72 100644
> --- a/drivers/gpu/drm/xe/xe_tile_types.h
> +++ b/drivers/gpu/drm/xe/xe_tile_types.h
> @@ -106,8 +106,6 @@ struct xe_tile {
>  			struct xe_lmtt lmtt;
>  		} pf;
>  		struct {
> -			/** @sriov.vf.ggtt_balloon: GGTT regions excluded from use. */
> -			struct xe_ggtt_node *ggtt_balloon[2];
>  			/** @sriov.vf.self_config: VF configuration data */
>  			struct xe_tile_sriov_vf_selfconfig self_config;
>  		} vf;

Can't believe I missed that. Must have slipped when rebasing.

Reviewed-by: Maarten Lankhorst <dev@lankhorst.se>

      parent reply	other threads:[~2026-05-11  6:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-10 20:56 [PATCH] drm/xe: Drop unused ggtt_balloon field Michal Wajdeczko
2026-05-10 21:03 ` ✓ CI.KUnit: success for " Patchwork
2026-05-10 21:51 ` ✓ Xe.CI.BAT: " Patchwork
2026-05-10 23:09 ` ✓ Xe.CI.FULL: " Patchwork
2026-05-11  6:58 ` Maarten Lankhorst [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=56f80dfc-4a87-4423-8ce1-e94e6c60ace6@lankhorst.se \
    --to=dev@lankhorst.se \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).