From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ankit Nautiyal <ankit.k.nautiyal@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
Subject: Re: [PATCH 8/9] drm/i915/intel_lt_phy: Fix the SPDX identifier comment
Date: Mon, 05 Jan 2026 14:17:28 +0200 [thread overview]
Message-ID: <d4a4a93aadaa092293ca53c970ed0733fe15425a@intel.com> (raw)
In-Reply-To: <20260105113544.574323-9-ankit.k.nautiyal@intel.com>
On Mon, 05 Jan 2026, Ankit Nautiyal <ankit.k.nautiyal@intel.com> wrote:
> Fix the SPDX identifier comment as per the licensing rules [1].
>
> [1] https://www.kernel.org/doc/html/latest/process/license-rules.html
>
> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_lt_phy.h | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_lt_phy.h b/drivers/gpu/drm/i915/display/intel_lt_phy.h
> index 7659c92b6c3c..83fff7b6a961 100644
> --- a/drivers/gpu/drm/i915/display/intel_lt_phy.h
> +++ b/drivers/gpu/drm/i915/display/intel_lt_phy.h
> @@ -1,4 +1,5 @@
> -/* SPDX-License-Identifier: MIT
> +/* SPDX-License-Identifier: MIT */
> +/*
> *
Please remove the superfluous blank line here.
> * Copyright © 2025 Intel Corporation
> */
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-01-05 12:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 11:35 [PATCH 0/9] drm/i915/display: Fix the SPDX license identifier for C headers Ankit Nautiyal
2026-01-05 11:35 ` [PATCH 1/9] drm/i915/intel_alpm: Fix the SPDX identifier comment Ankit Nautiyal
2026-01-05 11:35 ` [PATCH 2/9] drm/i915/intel_cx0_phy: " Ankit Nautiyal
2026-01-05 11:35 ` [PATCH 3/9] drm/i915/intel_cx0_phy_regs: " Ankit Nautiyal
2026-01-05 11:35 ` [PATCH 4/9] drm/i915/intel_display_params: " Ankit Nautiyal
2026-01-05 11:35 ` [PATCH 5/9] drm/i915/intel_dsb: " Ankit Nautiyal
2026-01-05 11:35 ` [PATCH 6/9] drm/i915/intel_dsb_buffer: " Ankit Nautiyal
2026-01-05 11:35 ` [PATCH 7/9] drm/i915/intel_gvt_api: " Ankit Nautiyal
2026-01-05 11:35 ` [PATCH 8/9] drm/i915/intel_lt_phy: " Ankit Nautiyal
2026-01-05 12:17 ` Jani Nikula [this message]
2026-01-05 12:19 ` [PATCH v2 " Ankit Nautiyal
2026-01-05 11:35 ` [PATCH 9/9] drm/i915/lt_phy_regs: " Ankit Nautiyal
2026-01-05 12:18 ` [PATCH 0/9] drm/i915/display: Fix the SPDX license identifier for C headers Jani Nikula
2026-01-07 4:30 ` Nautiyal, Ankit K
2026-01-05 12:25 ` ✓ CI.KUnit: success for " Patchwork
2026-01-05 12:41 ` ✗ CI.checksparse: warning " Patchwork
2026-01-05 13:00 ` ✓ Xe.CI.BAT: success " Patchwork
2026-01-05 13:07 ` ✓ CI.KUnit: success for drm/i915/display: Fix the SPDX license identifier for C headers (rev2) Patchwork
2026-01-05 13:22 ` ✗ CI.checksparse: warning " Patchwork
2026-01-05 13:50 ` ✓ Xe.CI.BAT: success " Patchwork
2026-01-05 14:50 ` ✗ Xe.CI.Full: failure for drm/i915/display: Fix the SPDX license identifier for C headers Patchwork
2026-01-05 16:17 ` ✗ Xe.CI.Full: failure for drm/i915/display: Fix the SPDX license identifier for C headers (rev2) 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=d4a4a93aadaa092293ca53c970ed0733fe15425a@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--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