From: Jani Nikula <jani.nikula@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: "Matt Roper" <matthew.d.roper@intel.com>,
intel-xe@lists.freedesktop.org,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Shekhar Chauhan" <shekhar.chauhan@intel.com>,
"Matt Atwood" <matthew.s.atwood@intel.com>
Subject: Re: xe generated headers (was: Re: [PATCH] drm/xe/ptl: L3bank mask is not available on the media GT)
Date: Wed, 09 Oct 2024 19:33:38 +0300 [thread overview]
Message-ID: <87cyk98cd9.fsf@intel.com> (raw)
In-Reply-To: <jyqqbtftdd654f3zjdaspygedv5lusi4tmzpnk3dqlylmmbd6v@mehvg5dd56zu>
On Wed, 09 Oct 2024, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> I like to keep the "generated" in the name since it's then clear
> that file isn't in the source checkout, but one should look at build
> directory instead. And even if someone mixes the build and source dir,
> there's no possibility of a clash.
Ack.
> I view this differently than what you are writting above. There is no
> "system/global" includes in the kernel. There are only the include paths
> passed to the compiler and the only difference between " and < is that
> for the former the compiler will *first* try to find the file relative
> to the compilation unit.
I think generally the headers under top level include/ are included
using <> and the rest using "", regardless of which paths were passed to
the compiler. In that sense, they are the "system/global" includes, even
if that doesn't match the conventional meaning.
A little bit of git grep suggests <> outnumbers "" for includes in
include/ by a factor of 100x.
BR,
Jani.
--
Jani Nikula, Intel
prev parent reply other threads:[~2024-10-09 16:33 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 ` xe generated headers (was: Re: [PATCH] drm/xe/ptl: L3bank mask is not available on the media GT) Jani Nikula
2024-10-09 15:34 ` Lucas De Marchi
2024-10-09 16:33 ` Jani Nikula [this message]
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=87cyk98cd9.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.