Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [Intel-gfx] [PATCH 2/2] drm/i915: fix Sphinx indentation warning
Date: Wed, 21 Jun 2023 15:31:56 +0300	[thread overview]
Message-ID: <20230621123156.14907-2-jani.nikula@intel.com> (raw)
In-Reply-To: <20230621123156.14907-1-jani.nikula@intel.com>

Fix Sphinx warning about unexpected indent.

Signed-off-by: Jani Nikula <jani.nikula@intel.com>
---
 drivers/gpu/drm/i915/gt/uc/intel_huc.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/gpu/drm/i915/gt/uc/intel_huc.c b/drivers/gpu/drm/i915/gt/uc/intel_huc.c
index bb95bdd1c3f9..23aa1b0e0166 100644
--- a/drivers/gpu/drm/i915/gt/uc/intel_huc.c
+++ b/drivers/gpu/drm/i915/gt/uc/intel_huc.c
@@ -26,6 +26,7 @@
  * The kernel driver is only responsible for loading the HuC firmware and
  * triggering its security authentication. This is done differently depending
  * on the platform:
+ *
  * - older platforms (from Gen9 to most Gen12s): the load is performed via DMA
  *   and the authentication via GuC
  * - DG2: load and authentication are both performed via GSC.
@@ -33,6 +34,7 @@
  *   not-DG2 older platforms), while the authentication is done in 2-steps,
  *   a first auth for clear-media workloads via GuC and a second one for all
  *   workloads via GSC.
+ *
  * On platforms where the GuC does the authentication, to correctly do so the
  * HuC binary must be loaded before the GuC one.
  * Loading the HuC is optional; however, not using the HuC might negatively
-- 
2.39.2


  reply	other threads:[~2023-06-21 12:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-21 12:31 [Intel-gfx] [PATCH 1/2] drm/doc: fix duplicate declaration warning Jani Nikula
2023-06-21 12:31 ` Jani Nikula [this message]
2023-06-26 12:05   ` [Intel-gfx] [PATCH 2/2] drm/i915: fix Sphinx indentation warning Luca Coelho
2023-06-21 21:13 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/doc: fix duplicate declaration warning Patchwork
2023-06-21 21:31 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-06-26  9:24 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/doc: fix duplicate declaration warning (rev2) Patchwork
2023-06-26  9:35 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-06-26 12:05 ` [Intel-gfx] [PATCH 1/2] drm/doc: fix duplicate declaration warning Luca Coelho
2023-06-26 17:18   ` Jani Nikula
2023-06-26 16:02 ` [Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/2] drm/doc: fix duplicate declaration warning (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=20230621123156.14907-2-jani.nikula@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@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