Linux Documentation
 help / color / mirror / Atom feed
From: Rafael Passos <rafael@rcpassos.me>
To: linux-doc@vger.kernel.org
Cc: corbet@lwn.net, skhan@linuxfoundation.org
Subject: [PATCH 1/3] Documentation: iio: fix Malformed table for ltc4283
Date: Sat, 20 Jun 2026 17:16:33 -0300	[thread overview]
Message-ID: <20260620201732.94141-2-rafael@rcpassos.me> (raw)
In-Reply-To: <20260620201732.94141-1-rafael@rcpassos.me>

Longest line in the first column is 27 chars

Signed-off-by: Rafael Passos <rafael@rcpassos.me>
---
 Documentation/hwmon/ltc4283.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/hwmon/ltc4283.rst b/Documentation/hwmon/ltc4283.rst
index a650c595bc8f..44a58ac6ee81 100644
--- a/Documentation/hwmon/ltc4283.rst
+++ b/Documentation/hwmon/ltc4283.rst
@@ -256,7 +256,7 @@ these logs can be cleared by writing in the proper reset_history attribute.
 ``/sys/kernel/debug/i2c/i2c-[X]/[X]-addr/``
 contains the following attributes:
 
-=======================		==========================================
+===========================  ===========================================================
 power1_failed_fault_log		Set to 1 by a power1 fault occurring.
 power1_good_input_fault_log	Set to 1 by a power1 good input fault occurring at PGIO3.
 in11_fet_short_fault_log	Set to 1 when a FET-short fault occurs.
@@ -264,4 +264,4 @@ in11_fet_bad_fault_log		Set to 1 when a FET-BAD fault occurs.
 in0_lcrit_fault_log		Set to 1 by a VIN undervoltage fault occurring.
 in0_crit_fault_log		Set to 1 by a VIN overvoltage fault occurring.
 curr1_crit_fault_log		Set to 1 by an overcurrent fault occurring.
-======================= 	==========================================
+===========================  ===========================================================
-- 
2.53.0


  reply	other threads:[~2026-06-20 20:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-20 20:16 [PATCH 0/3] Documentation: fix doc build errors for 7.2 Rafael Passos
2026-06-20 20:16 ` Rafael Passos [this message]
2026-06-20 21:29   ` [PATCH 1/3] Documentation: iio: fix Malformed table for ltc4283 Randy Dunlap
2026-06-20 20:16 ` [PATCH 2/3] Documentation: xe_drm: fix chars used for subsection Rafael Passos
2026-06-20 21:42   ` Randy Dunlap
2026-06-21  2:38     ` Rafael Passos
2026-06-21  3:43       ` Randy Dunlap
2026-06-20 20:16 ` [PATCH 3/3] Documentation: ABI: fix description field indentation Rafael Passos
2026-06-20 21:33   ` Randy Dunlap

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=20260620201732.94141-2-rafael@rcpassos.me \
    --to=rafael@rcpassos.me \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=skhan@linuxfoundation.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