From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Francois Dugast <francois.dugast@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [PATCH i-g-t] drm-uapi/xe: Ensure every uapi struct has drm_xe prefix
Date: Thu, 14 Dec 2023 19:51:51 -0500 [thread overview]
Message-ID: <ZXujJ7DX0br9KlbL@intel.com> (raw)
In-Reply-To: <20231214194925.7-1-francois.dugast@intel.com>
On Thu, Dec 14, 2023 at 07:49:25PM +0000, Francois Dugast wrote:
> Align with commit ("drm/xe/uapi: Ensure every uapi struct has drm_xe prefix")
>
> Signed-off-by: Francois Dugast <francois.dugast@intel.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> include/drm-uapi/xe_drm.h | 18 +++++++++---------
> tests/intel/xe_mmap.c | 2 +-
> 2 files changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/include/drm-uapi/xe_drm.h b/include/drm-uapi/xe_drm.h
> index b1839df48..9609194c1 100644
> --- a/include/drm-uapi/xe_drm.h
> +++ b/include/drm-uapi/xe_drm.h
> @@ -27,7 +27,7 @@ extern "C" {
> #define DRM_XE_RESET_FAILED_UEVENT "DEVICE_STATUS"
>
> /**
> - * struct xe_user_extension - Base class for defining a chain of extensions
> + * struct drm_xe_user_extension - Base class for defining a chain of extensions
> *
> * Many interfaces need to grow over time. In most cases we can simply
> * extend the struct and have userspace pass in more data. Another option,
> @@ -45,29 +45,29 @@ extern "C" {
> *
> * .. code-block:: C
> *
> - * struct xe_user_extension ext3 {
> + * struct drm_xe_user_extension ext3 {
> * .next_extension = 0, // end
> * .name = ...,
> * };
> - * struct xe_user_extension ext2 {
> + * struct drm_xe_user_extension ext2 {
> * .next_extension = (uintptr_t)&ext3,
> * .name = ...,
> * };
> - * struct xe_user_extension ext1 {
> + * struct drm_xe_user_extension ext1 {
> * .next_extension = (uintptr_t)&ext2,
> * .name = ...,
> * };
> *
> - * Typically the struct xe_user_extension would be embedded in some uAPI
> + * Typically the struct drm_xe_user_extension would be embedded in some uAPI
> * struct, and in this case we would feed it the head of the chain(i.e ext1),
> * which would then apply all of the above extensions.
> *
> */
> -struct xe_user_extension {
> +struct drm_xe_user_extension {
> /**
> * @next_extension:
> *
> - * Pointer to the next struct xe_user_extension, or zero if the end.
> + * Pointer to the next struct drm_xe_user_extension, or zero if the end.
> */
> __u64 next_extension;
>
> @@ -78,7 +78,7 @@ struct xe_user_extension {
> *
> * Also note that the name space for this is not global for the whole
> * driver, but rather its scope/meaning is limited to the specific piece
> - * of uAPI which has embedded the struct xe_user_extension.
> + * of uAPI which has embedded the struct drm_xe_user_extension.
> */
> __u32 name;
>
> @@ -625,7 +625,7 @@ struct drm_xe_gem_mmap_offset {
> /** struct drm_xe_ext_set_property - XE set property extension */
> struct drm_xe_ext_set_property {
> /** @base: base user extension */
> - struct xe_user_extension base;
> + struct drm_xe_user_extension base;
>
> /** @property: property to set */
> __u32 property;
> diff --git a/tests/intel/xe_mmap.c b/tests/intel/xe_mmap.c
> index 63fdf46a8..e96192d23 100644
> --- a/tests/intel/xe_mmap.c
> +++ b/tests/intel/xe_mmap.c
> @@ -92,7 +92,7 @@ static void test_bad_flags(int fd)
> static void test_bad_extensions(int fd)
> {
> uint64_t size = xe_get_default_alignment(fd);
> - struct xe_user_extension ext;
> + struct drm_xe_user_extension ext;
> struct drm_xe_gem_mmap_offset mmo = {
> .handle = xe_bo_create(fd, 0, size,
> vram_if_possible(fd, 0),
> --
> 2.34.1
>
prev parent reply other threads:[~2023-12-15 0:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 19:49 [PATCH i-g-t] drm-uapi/xe: Ensure every uapi struct has drm_xe prefix Francois Dugast
2023-12-14 21:08 ` ✓ Fi.CI.BAT: success for " Patchwork
2023-12-14 21:35 ` ✓ CI.xeBAT: " Patchwork
2023-12-14 21:57 ` ✗ Fi.CI.IGT: failure " Patchwork
2023-12-15 0:51 ` Rodrigo Vivi [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=ZXujJ7DX0br9KlbL@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=francois.dugast@intel.com \
--cc=igt-dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox