All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 4/4] drm/xe: Fix xe_reg_sr.h
Date: Mon, 13 May 2024 11:45:04 -0400	[thread overview]
Message-ID: <ZkI1gHQNUktkLmz1@intel.com> (raw)
In-Reply-To: <20240513084218.2084-5-michal.wajdeczko@intel.com>

On Mon, May 13, 2024 at 10:42:18AM +0200, Michal Wajdeczko wrote:
> Prefer forward declarations over #include xe_reg_sr_types.h

Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>

> 
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> ---
>  drivers/gpu/drm/xe/xe_reg_sr.h | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_reg_sr.h b/drivers/gpu/drm/xe/xe_reg_sr.h
> index e3197c33afe2..51fbba423e27 100644
> --- a/drivers/gpu/drm/xe/xe_reg_sr.h
> +++ b/drivers/gpu/drm/xe/xe_reg_sr.h
> @@ -6,8 +6,6 @@
>  #ifndef _XE_REG_SR_
>  #define _XE_REG_SR_
>  
> -#include "xe_reg_sr_types.h"
> -
>  /*
>   * Reg save/restore bookkeeping
>   */
> @@ -15,6 +13,8 @@
>  struct xe_device;
>  struct xe_gt;
>  struct xe_hw_engine;
> +struct xe_reg_sr;
> +struct xe_reg_sr_entry;
>  struct drm_printer;
>  
>  int xe_reg_sr_init(struct xe_reg_sr *sr, const char *name, struct xe_device *xe);
> -- 
> 2.43.0
> 

  reply	other threads:[~2024-05-13 15:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-13  8:42 [PATCH 0/4] Fix few more headers Michal Wajdeczko
2024-05-13  8:42 ` [PATCH 1/4] drm/xe: Fix xe_gt_throttle_sysfs.h Michal Wajdeczko
2024-05-13 15:44   ` Rodrigo Vivi
2024-05-13  8:42 ` [PATCH 2/4] drm/xe: Fix xe_guc_ads.h Michal Wajdeczko
2024-05-13 15:44   ` Rodrigo Vivi
2024-05-13  8:42 ` [PATCH 3/4] drm/xe: Fix xe_lrc.h Michal Wajdeczko
2024-05-13 15:44   ` Rodrigo Vivi
2024-05-13  8:42 ` [PATCH 4/4] drm/xe: Fix xe_reg_sr.h Michal Wajdeczko
2024-05-13 15:45   ` Rodrigo Vivi [this message]
2024-05-13  9:35 ` ✓ CI.Patch_applied: success for Fix few more headers Patchwork
2024-05-13  9:35 ` ✓ CI.checkpatch: " Patchwork
2024-05-13  9:36 ` ✓ CI.KUnit: " Patchwork
2024-05-13  9:47 ` ✓ CI.Build: " Patchwork
2024-05-13  9:50 ` ✓ CI.Hooks: " Patchwork
2024-05-13  9:51 ` ✓ CI.checksparse: " Patchwork
2024-05-13 10:17 ` ✓ CI.BAT: " Patchwork
2024-05-13 11:26 ` ✗ CI.FULL: failure " Patchwork
2024-05-13 17:19   ` 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=ZkI1gHQNUktkLmz1@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.