mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "Naveen Krishna Chatradhi" <naveenkrishna.chatradhi@amd.com>,
	"Carlos Bilbao" <carlos.bilbao.osdev@gmail.com>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Ingo Molnar" <mingo@redhat.com>,
	"Borislav Petkov" <bp@alien8.de>,
	"Dave Hansen" <dave.hansen@linux.intel.com>,
	x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Suma Hegde" <suma.hegde@amd.com>,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: [PATCH 1/1] Documentation/x86/amd/hsmp: Fix ACPI dump formatting
Date: Thu, 24 Oct 2024 16:00:46 +0300	[thread overview]
Message-ID: <20241024130046.31753-1-ilpo.jarvinen@linux.intel.com> (raw)

hsmp documentation added into pdx86 for-next branch triggers these
error:

86: ERROR: Unexpected indentation.
87: WARNING: Block quote ends without a blank line; unexpected unindent.
90: ERROR: Unexpected indentation.
91: WARNING: Block quote ends without a blank line; unexpected unindent.
94: ERROR: Unexpected indentation.
96: ERROR: Unexpected indentation.
97: WARNING: Block quote ends without a blank line; unexpected unindent.
100: ERROR: Unexpected indentation.
101: WARNING: Block quote ends without a blank line; unexpected unindent.
102: WARNING: Block quote ends without a blank line; unexpected unindent.
105: ERROR: Unexpected indentation.
107: ERROR: Unexpected indentation.
109: WARNING: Block quote ends without a blank line; unexpected unindent.
112: ERROR: Unexpected indentation.
115: WARNING: Block quote ends without a blank line; unexpected unindent.
116: WARNING: Block quote ends without a blank line; unexpected unindent.
117: WARNING: Definition list ends without a blank line; unexpected unindent.

Convert the problematic ACPI dump fragment to use preformatted text.

My plan is to fold this commit into the original commit.

Fixes: f9ad7a2843a6 ("platform/x86/amd/hsmp: Create separate ACPI, plat and common drivers")
Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
---
 Documentation/arch/x86/amd_hsmp.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/arch/x86/amd_hsmp.rst b/Documentation/arch/x86/amd_hsmp.rst
index abf1fa3230d9..2fd917638e42 100644
--- a/Documentation/arch/x86/amd_hsmp.rst
+++ b/Documentation/arch/x86/amd_hsmp.rst
@@ -74,9 +74,9 @@ The same is defined in the amd_hsmp.h header.
 ACPI device object format
 =========================
 The ACPI object format expected from the amd_hsmp driver
-for socket with ID00 is given below.
+for socket with ID00 is given below::
 
-Device(HSMP)
+  Device(HSMP)
 		{
 			Name(_HID, "AMDI0097")
 			Name(_UID, "ID00")
-- 
2.39.5


                 reply	other threads:[~2024-10-24 13:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20241024130046.31753-1-ilpo.jarvinen@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=carlos.bilbao.osdev@gmail.com \
    --cc=corbet@lwn.net \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=naveenkrishna.chatradhi@amd.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=suma.hegde@amd.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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

all inboxes | Powered by JetHome®