From: Jani Nikula <jani.nikula@linux.intel.com>
To: Francois Dugast <francois.dugast@intel.com>,
intel-xe@lists.freedesktop.org
Cc: Francois Dugast <francois.dugast@intel.com>
Subject: Re: [Intel-xe] [PATCH 1/2] fixup! drm/xe: Introduce a new DRM driver for Intel GPUs
Date: Thu, 06 Jul 2023 17:49:01 +0300 [thread overview]
Message-ID: <87mt09jdsy.fsf@intel.com> (raw)
In-Reply-To: <20230706142728.6-2-francois.dugast@intel.com>
On Thu, 06 Jul 2023, Francois Dugast <francois.dugast@intel.com> wrote:
> Fix some SPDX license identifier warnings reported by checkpatch.
>
> Signed-off-by: Francois Dugast <francois.dugast@intel.com>
> ---
> drivers/gpu/drm/xe/xe_map.h | 2 +-
> drivers/gpu/drm/xe/xe_trace.c | 2 +-
> drivers/gpu/drm/xe/xe_trace.h | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_map.h b/drivers/gpu/drm/xe/xe_map.h
> index 032c2e8b5438..f62e0c8b67ab 100644
> --- a/drivers/gpu/drm/xe/xe_map.h
> +++ b/drivers/gpu/drm/xe/xe_map.h
> @@ -1,4 +1,4 @@
> -// SPDX-License-Identifier: MIT
> +/* SPDX-License-Identifier: MIT */
> /*
> * Copyright © 2022 Intel Corporation
> */
> diff --git a/drivers/gpu/drm/xe/xe_trace.c b/drivers/gpu/drm/xe/xe_trace.c
> index 1026fb37f75b..70c8a5f1a9ca 100644
> --- a/drivers/gpu/drm/xe/xe_trace.c
> +++ b/drivers/gpu/drm/xe/xe_trace.c
> @@ -1,4 +1,4 @@
> -// SPDX-Liense-Identifier: GPL-2.0
> +// SPDX-License-Identifier: MIT
The trace system is GPL-2.0, and all trace users are innately tied to
the guts of it, not linked to. Usually trace stuff has been GPL-2.0 for
this reason.
> /*
> * Copyright © 2022 Intel Corporation
> */
> diff --git a/drivers/gpu/drm/xe/xe_trace.h b/drivers/gpu/drm/xe/xe_trace.h
> index 02861c26e145..b92ad4ab1c79 100644
> --- a/drivers/gpu/drm/xe/xe_trace.h
> +++ b/drivers/gpu/drm/xe/xe_trace.h
> @@ -1,4 +1,4 @@
> -/* SPDX-Liense-Identifier: GPL-2.0 */
> +/* SPDX-License-Identifier: MIT */
Ditto.
> /*
> * Copyright © 2022 Intel Corporation
> */
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-07-06 14:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 14:27 [Intel-xe] [PATCH 0/2] Fix SPDX license identifiers Francois Dugast
2023-07-06 14:27 ` [Intel-xe] [PATCH 1/2] fixup! drm/xe: Introduce a new DRM driver for Intel GPUs Francois Dugast
2023-07-06 14:49 ` Jani Nikula [this message]
2023-07-06 14:27 ` [Intel-xe] [PATCH 2/2] fixup! drm/xe/display: Implement display support Francois Dugast
2023-07-06 14:46 ` Jani Nikula
2023-07-07 20:48 ` Lucas De Marchi
2023-07-06 14:41 ` [Intel-xe] ✓ CI.Patch_applied: success for Fix SPDX license identifiers Patchwork
2023-07-06 14:42 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-07-06 14:43 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-07-06 14:47 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-07-06 14:47 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-07-06 14:48 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-07-06 15:34 ` [Intel-xe] ○ CI.BAT: info " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2023-08-04 23:17 [Intel-xe] [PATCH 0/2] Update ARL-S device IDs Lucas De Marchi
2023-08-04 23:17 ` [Intel-xe] [PATCH 1/2] fixup! drm/xe: Introduce a new DRM driver for Intel GPUs Lucas De Marchi
2023-08-07 2:50 ` Niranjana Vishwanathapura
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=87mt09jdsy.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=francois.dugast@intel.com \
--cc=intel-xe@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