Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
	intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH v9 1/3] fault-inject: Include linux/types.h by default.
Date: Fri, 28 Jul 2023 12:49:56 -0400	[thread overview]
Message-ID: <ZMPxtBs6T3lODcgV@intel.com> (raw)
In-Reply-To: <20230726232650.3873897-2-himal.prasad.ghimiray@intel.com>

On Thu, Jul 27, 2023 at 04:56:48AM +0530, Himal Prasad Ghimiray wrote:
> Functions should_fail_alloc_page, should_failslab, and __should_failslab
> are declared irrespective of CONFIG_FAULT_INJECTION. These functions use
> bool and gfp_t types, which are treated as unknown when
> CONFIG_FAULT_INJECTION is disabled because the inclusion of linux/types.h
> is missing.
> 
> Fixes: 6ff1cb355e62 ("[PATCH] fault-injection capabilities infrastructure")
> 
> Cc: Lucas De Marchi <lucas.demarchi@intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Cc: Badal Nilawar <badal.nilawar@intel.com>
> Signed-off-by: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
> ---
> v2:
> - Add fixes tag (Badal)
> - Rectify Cc. (Lucas)

and now you removed the correct cc folks..

Okay, so, I'm pushing this exact version to our drm-xe-next in a hope that
we will get this patch sorted out before we are ready for the first
pull request towards drm-next...

We will later remove this patch anyway before the drm-next submission and
only add as a topic/core-for-CI if still needed.

Himal, please continue working with the community there to get this
fixed upstream. Resend the v2 standalone, but without the version history to
the lklm and to the maintainers.

> 
>  include/linux/fault-inject.h | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/include/linux/fault-inject.h b/include/linux/fault-inject.h
> index 481abf530b3c..f83ab2b6cd08 100644
> --- a/include/linux/fault-inject.h
> +++ b/include/linux/fault-inject.h
> @@ -2,9 +2,10 @@
>  #ifndef _LINUX_FAULT_INJECT_H
>  #define _LINUX_FAULT_INJECT_H
>  
> +#include <linux/types.h>
> +
>  #ifdef CONFIG_FAULT_INJECTION
>  
> -#include <linux/types.h>
>  #include <linux/debugfs.h>
>  #include <linux/configfs.h>
>  #include <linux/ratelimit.h>
> -- 
> 2.25.1
> 

  reply	other threads:[~2023-07-28 16:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-26 23:26 [Intel-xe] [PATCH v9 0/3] Notify userspace about uevent failure Himal Prasad Ghimiray
2023-07-26 23:26 ` [Intel-xe] [PATCH v9 1/3] fault-inject: Include linux/types.h by default Himal Prasad Ghimiray
2023-07-28 16:49   ` Rodrigo Vivi [this message]
2023-07-26 23:26 ` [Intel-xe] [PATCH v9 2/3] drm/xe: Notify Userspace when gt reset fails Himal Prasad Ghimiray
2023-07-26 23:26 ` [Intel-xe] [PATCH v9 3/3] drm/xe: Introduce fault injection for gt reset Himal Prasad Ghimiray
2023-07-31 14:30   ` Balasubramani Vivekanandan
2023-07-31 15:24     ` Ghimiray, Himal Prasad
2023-08-01  6:02       ` Balasubramani Vivekanandan
2023-08-01  6:45         ` Ghimiray, Himal Prasad
2023-08-01  8:03           ` Balasubramani Vivekanandan
2023-08-01  8:04             ` Ghimiray, Himal Prasad
2023-07-27  0:29 ` [Intel-xe] ✓ CI.Patch_applied: success for Notify userspace about uevent failure Patchwork
2023-07-27  0:29 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-07-27  0:30 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-07-27  0:34 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-07-27  0:35 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-07-27  0:36 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-07-27  1:10 ` [Intel-xe] ○ CI.BAT: info " 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=ZMPxtBs6T3lODcgV@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=himal.prasad.ghimiray@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@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