public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: linux-doc@vger.kernel.org
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
	kernel test robot <lkp@intel.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Kuppuswamy Sathyanarayanan 
	<sathyanarayanan.kuppuswamy@linux.intel.com>,
	Andi Kleen <ak@linux.intel.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH] Documentation: tdx: fix tainted kernels table
Date: Sat, 16 Jul 2022 10:44:32 +0700	[thread overview]
Message-ID: <20220716034432.207574-1-bagasdotme@gmail.com> (raw)
In-Reply-To: <202207150911.eR0W0c9D-lkp@intel.com>

kernel test robot reported htmldocs warning on guest-filter branch of
tdx tree:

Documentation/admin-guide/tainted-kernels.rst:82: WARNING: Malformed table.

The full warning is:

Documentation/admin-guide/tainted-kernels.rst:82: WARNING: Malformed table.
Bottom/header table border does not match top border.

===  ===  ======  ========================================================
Bit  Log  Number  Reason that got the kernel tainted
===  ===  ======  ========================================================
<content snipped>
===  ===  ======  =========================================================

Fix the warning by matching header border length with bottom border.

Link: https://lore.kernel.org/linux-doc/202207150911.eR0W0c9D-lkp@intel.com/
Fixes: 7acbe4e1dcfb9d ("Add taint flag for TDX overrides")
Reported-by: kernel test robot <lkp@intel.com>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
Cc: Andi Kleen <ak@linux.intel.com>
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
 tdx tree is at https://github.com/intel/tdx.git

 Documentation/admin-guide/tainted-kernels.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/admin-guide/tainted-kernels.rst b/Documentation/admin-guide/tainted-kernels.rst
index 65c58092ec354b..1146bce7e32e49 100644
--- a/Documentation/admin-guide/tainted-kernels.rst
+++ b/Documentation/admin-guide/tainted-kernels.rst
@@ -79,9 +79,9 @@ which bits are set::
 Table for decoding tainted state
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-===  ===  ======  ========================================================
+===  ===  ======  =========================================================
 Bit  Log  Number  Reason that got the kernel tainted
-===  ===  ======  ========================================================
+===  ===  ======  =========================================================
   0  G/P       1  proprietary module was loaded
   1  _/F       2  module was force loaded
   2  _/S       4  kernel running on an out of specification system

base-commit: 0a555e67b143701a81612d819e693cf5786de418
-- 
An old man doll... just what I always wanted! - Clara


      reply	other threads:[~2022-07-16  3:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-15  1:55 [intel-tdx:guest-filter 8/28] htmldocs: Documentation/admin-guide/tainted-kernels.rst:82: WARNING: Malformed table kernel test robot
2022-07-16  3:44 ` Bagas Sanjaya [this message]

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=20220716034432.207574-1-bagasdotme@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=ak@linux.intel.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=sathyanarayanan.kuppuswamy@linux.intel.com \
    /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