From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Matt Roper" <matthew.d.roper@intel.com>,
intel-xe@lists.freedesktop.org,
"Lucas De Marchi" <lucas.demarchi@intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Cc: matthew.d.roper@intel.com,
Shekhar Chauhan <shekhar.chauhan@intel.com>,
Matt Atwood <matthew.s.atwood@intel.com>
Subject: xe generated headers (was: Re: [PATCH] drm/xe/ptl: L3bank mask is not available on the media GT)
Date: Wed, 09 Oct 2024 14:55:59 +0300 [thread overview]
Message-ID: <878quxa3sg.fsf@intel.com> (raw)
In-Reply-To: <20241004212037.1431184-2-matthew.d.roper@intel.com>
On Fri, 04 Oct 2024, Matt Roper <matthew.d.roper@intel.com> wrote:
> diff --git a/drivers/gpu/drm/xe/xe_gt_topology.c b/drivers/gpu/drm/xe/xe_gt_topology.c
> index 651ba53623e5..df2042db7ee6 100644
> --- a/drivers/gpu/drm/xe/xe_gt_topology.c
> +++ b/drivers/gpu/drm/xe/xe_gt_topology.c
> @@ -5,6 +5,7 @@
>
> #include "xe_gt_topology.h"
>
> +#include <generated/xe_wa_oob.h>
Hijacking the thread here a bit, sorry.
This use of system include path <> instead of "" for xe generated
headers keeps bugging me.
There's a global directory for generated headers, and that's what
<generated/...> usually means. See:
git grep -h "#include <generated/" | sort | uniq
Or look at top level include/generated in the build directory.
Especially putting #include <generated/...> next to #include <linux/...>
implies we're referring to the system generated headers, but we're not.
I think we should be using #include "generated/xe_wa_oob.h" instead,
possibly with a completely different subdirectory name to not have the
name collision and confusion at all.
Another alternative is to do this in the Makefile:
subdir-ccflags-y += -I$(obj)/generated -I$(src)
and just use #include "xe_wa_oob.h" directly. (FWIW this is what msm
does.)
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-10-09 11:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 21:20 [PATCH] drm/xe/ptl: L3bank mask is not available on the media GT Matt Roper
2024-10-07 13:00 ` Gustavo Sousa
2024-10-07 13:59 ` ✓ CI.Patch_applied: success for " Patchwork
2024-10-07 14:00 ` ✓ CI.checkpatch: " Patchwork
2024-10-07 14:02 ` ✓ CI.KUnit: " Patchwork
2024-10-07 14:15 ` ✓ CI.Build: " Patchwork
2024-10-07 14:17 ` ✓ CI.Hooks: " Patchwork
2024-10-07 14:19 ` ✓ CI.checksparse: " Patchwork
2024-10-07 14:50 ` ✓ CI.BAT: " Patchwork
2024-10-08 6:45 ` ✗ CI.FULL: failure " Patchwork
2024-10-09 11:55 ` Jani Nikula [this message]
2024-10-09 15:34 ` xe generated headers (was: Re: [PATCH] drm/xe/ptl: L3bank mask is not available on the media GT) Lucas De Marchi
2024-10-09 16:33 ` Jani Nikula
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=878quxa3sg.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=matthew.s.atwood@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=shekhar.chauhan@intel.com \
--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.