All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Gustavo Sousa <gustavo.sousa@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH] drm/xe: Include only relevant header in xe_module.h
Date: Thu, 4 May 2023 04:28:41 +0000	[thread overview]
Message-ID: <ZFM0ebZQ8SstMhaR@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <20230503174922.252111-1-gustavo.sousa@intel.com>

On Wed, May 03, 2023 at 02:49:22PM -0300, Gustavo Sousa wrote:
> Things defined in <linux/init.h> are not really used by that header.
> Replace that with <linux/types.h>, to have bool and u32 available.
> 
> Signed-off-by: Gustavo Sousa <gustavo.sousa@intel.com>

Reviewed-by: Matthew Brost <matthew.brost@intel.com>

> ---
>  drivers/gpu/drm/xe/xe_module.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_module.h b/drivers/gpu/drm/xe/xe_module.h
> index 86916c176382..7169907c3365 100644
> --- a/drivers/gpu/drm/xe/xe_module.h
> +++ b/drivers/gpu/drm/xe/xe_module.h
> @@ -3,7 +3,7 @@
>   * Copyright © 2023 Intel Corporation
>   */
>  
> -#include <linux/init.h>
> +#include <linux/types.h>
>  
>  /* Module modprobe variables */
>  extern bool enable_guc;
> -- 
> 2.40.0
> 

  parent reply	other threads:[~2023-05-04  4:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03 17:49 [Intel-xe] [PATCH] drm/xe: Include only relevant header in xe_module.h Gustavo Sousa
2023-05-03 17:52 ` [Intel-xe] ✓ CI.Patch_applied: success for " Patchwork
2023-05-03 17:53 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-05-03 17:57 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-05-03 18:22 ` [Intel-xe] ○ CI.BAT: info " Patchwork
2023-05-04  4:28 ` Matthew Brost [this message]
2023-05-04  7:40 ` [Intel-xe] [PATCH] " Lucas De Marchi

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=ZFM0ebZQ8SstMhaR@DUT025-TGLU.fm.intel.com \
    --to=matthew.brost@intel.com \
    --cc=gustavo.sousa@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    /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.