All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
Cc: "Himal Prasad Ghimiray" <himal.prasad.ghimiray@intel.com>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	intel-gfx@lists.freedesktop.org,
	"Lucas De Marchi" <lucas.demarchi@intel.com>,
	"Oded Gabbay" <ogabbay@kernel.org>
Subject: Re: [PATCH] drm/xe: Fix build without CONFIG_FAULT_INJECTION
Date: Mon, 18 Dec 2023 14:28:14 -0500	[thread overview]
Message-ID: <ZYCdTlH6DrCAM1ZI@intel.com> (raw)
In-Reply-To: <87a5q7uyy0.wl-ashutosh.dixit@intel.com>

On Mon, Dec 18, 2023 at 10:51:03AM -0800, Dixit, Ashutosh wrote:
> On Mon, 18 Dec 2023 06:57:14 -0800, Thomas Hellström wrote:
> >
> >
> > On 12/18/23 15:30, Rodrigo Vivi wrote:
> > > Ideally this header could be included without the CONFIG_FAULT_INJECTION
> > > and it would take care itself for the includes it needs.
> > > So, let's temporary workaround this by moving this below and including
> > > only when CONFIG_FAULT_INJECTION is selected to avoid build breakages.
> > >
> > > Another solution would be us including the linux/types.h as well, but
> > > this creates unnecessary cases.
> > >
> > > Reference: https://lore.kernel.org/all/20230816134748.979231-1-himal.prasad.ghimiray@intel.com/
> > > Cc: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
> > > Cc: Oded Gabbay <ogabbay@kernel.org>
> > > Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> > > Cc: Lucas De Marchi <lucas.demarchi@intel.com>
> > > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > LGTM.
> >
> > Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> 
> Hmm, msm/msm_drv.c doesn't seem to need to do this.

because it also imports the types.h:
drivers/gpu/drm/msm/msm_drv.h:#include <linux/types.h>

> Anyway maybe ok for a
> temporary fix...

yes, it is a temporary hammer.
But maybe we don't need this if Andrew acks to get this through
drm-xe-next -> drm-next:

https://lore.kernel.org/all/a5o2opdfsfnbptrrbvillogft2uqp73w4icu3mdmmwtvoqmdr2@y2fbrc6t4aew/

  reply	other threads:[~2023-12-18 19:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-18 14:30 [PATCH] drm/xe: Fix build without CONFIG_FAULT_INJECTION Rodrigo Vivi
2023-12-18 14:57 ` Thomas Hellström
2023-12-18 18:51   ` Dixit, Ashutosh
2023-12-18 19:28     ` Rodrigo Vivi [this message]
2023-12-18 21:33 ` ✗ Fi.CI.BUILD: failure for " 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=ZYCdTlH6DrCAM1ZI@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=ashutosh.dixit@intel.com \
    --cc=himal.prasad.ghimiray@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=ogabbay@kernel.org \
    --cc=thomas.hellstrom@linux.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.