Skip to contentSkip to conversation

docs/gpu: fix docs compile error for i915

PATCH In review Claudio Cambra 1 participant 2 messages Sep 6, 2023

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 docs/gpu: fix docs compile error for i915

Compile error was caused by improper doc comment whitespacing

Extra task for "Documentation task"
Linux kernel Bug Fixing Fall Unpaid 2023

---
 drivers/gpu/drm/i915/gt/uc/intel_huc.c | 2 ++
 1 file changed, 2 insertions(+)
drivers/gpu/drm/i915/gt/uc/intel_huc.c +2 -0
index ddd146265beb..fa70defcb5b2 100644
@@ -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
Signature · 1 line
2.41.0
#1 lore raw

Apologies, saw this has already been fixed, please disregard

Claudio

Quoted 30 lines · Claudio Cambra

Compile error was caused by improper doc comment whitespacing

Extra task for "Documentation task"
Linux kernel Bug Fixing Fall Unpaid 2023

---
  drivers/gpu/drm/i915/gt/uc/intel_huc.c | 2 ++
  1 file changed, 2 insertions(+)
drivers/gpu/drm/i915/gt/uc/intel_huc.c +2 -0
index ddd146265beb..fa70defcb5b2 100644
@@ -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