Linux Documentation
 help / color / mirror / Atom feed
From: Luis Felipe Hernandez <luis.hernandez093@gmail.com>
To: corbet@lwn.net
Cc: alexandre.belloni@bootlin.com, pisa@cmp.felk.cvut.cz,
	ondrej.ille@gmail.com, mkl@pengutronix.de,
	James.Bottomley@HansenPartnership.com,
	martin.petersen@oracle.com, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Luis Felipe Hernandez <luis.hernandez093@gmail.com>
Subject: [PATCH] docs: Fix kernel-doc indentation errors in multiple drivers
Date: Wed,  2 Jul 2025 22:35:11 -0400	[thread overview]
Message-ID: <20250703023511.82768-1-luis.hernandez093@gmail.com> (raw)

Fix kernel-doc formatting issues causing "Unexpected indentation"
errors during documentation build in CAN, SCSI, and I3C drivers.

Signed-off-by: Luis Felipe Hernandez <luis.hernandez093@gmail.com>
---
 drivers/i3c/device.c                     | 6 +++---
 drivers/net/can/ctucanfd/ctucanfd_base.c | 8 ++++----
 drivers/scsi/scsi.c                      | 4 ++--
 3 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/drivers/i3c/device.c b/drivers/i3c/device.c
index e80e48756914..7aec9c1e01b9 100644
--- a/drivers/i3c/device.c
+++ b/drivers/i3c/device.c
@@ -28,9 +28,9 @@
  *
  * Return: 0 in case of success, a negative error core otherwise.
  *	   -EAGAIN: controller lost address arbitration. Target
- *		    (IBI, HJ or controller role request) win the bus. Client
- *		    driver needs to resend the 'xfers' some time later.
- *		    See I3C spec ver 1.1.1 09-Jun-2021. Section: 5.1.2.2.3.
+ *	   (IBI, HJ or controller role request) win the bus. Client
+ *	   driver needs to resend the 'xfers' some time later.
+ *	   See I3C spec ver 1.1.1 09-Jun-2021. Section: 5.1.2.2.3.
  */
 int i3c_device_do_priv_xfers(struct i3c_device *dev,
 			     struct i3c_priv_xfer *xfers,
diff --git a/drivers/net/can/ctucanfd/ctucanfd_base.c b/drivers/net/can/ctucanfd/ctucanfd_base.c
index bf6398772960..bd6938f6e105 100644
--- a/drivers/net/can/ctucanfd/ctucanfd_base.c
+++ b/drivers/net/can/ctucanfd/ctucanfd_base.c
@@ -507,10 +507,10 @@ static bool ctucan_is_txt_buf_writable(struct ctucan_priv *priv, u8 buf)
  * @isfdf:	True - CAN FD Frame, False - CAN 2.0 Frame
  *
  * Return: True - Frame inserted successfully
- *	   False - Frame was not inserted due to one of:
- *			1. TXT Buffer is not writable (it is in wrong state)
- *			2. Invalid TXT buffer index
- *			3. Invalid frame length
+ *         False - Frame was not inserted due to one of:
+ *         1. TXT Buffer is not writable (it is in wrong state)
+ *         2. Invalid TXT buffer index
+ *         3. Invalid frame length
  */
 static bool ctucan_insert_frame(struct ctucan_priv *priv, const struct canfd_frame *cf, u8 buf,
 				bool isfdf)
diff --git a/drivers/scsi/scsi.c b/drivers/scsi/scsi.c
index 534310224e8f..5f46f593d44f 100644
--- a/drivers/scsi/scsi.c
+++ b/drivers/scsi/scsi.c
@@ -243,8 +243,8 @@ EXPORT_SYMBOL(scsi_change_queue_depth);
  * 		need to adjust the queue depth on the device.
  *
  * Returns:	0 - No change needed, >0 - Adjust queue depth to this new depth,
- * 		-1 - Drop back to untagged operation using host->cmd_per_lun
- * 			as the untagged command depth
+ *              -1 - Drop back to untagged operation using host->cmd_per_lun
+ *              as the untagged command depth
  *
  * Lock Status:	None held on entry
  *
-- 
2.50.0


             reply	other threads:[~2025-07-03  2:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-03  2:35 Luis Felipe Hernandez [this message]
2025-07-05 19:23 ` [PATCH] docs: Fix kernel-doc indentation errors in multiple drivers Pavel Pisa
2025-07-05 21:36   ` Randy Dunlap
2025-07-05 21:45     ` Randy Dunlap
2025-07-15  0:20       ` Bagas Sanjaya
2025-07-07  0:37     ` Bagas Sanjaya
2025-07-07  0:47       ` Randy Dunlap
2025-07-07 13:43       ` Felipe Hernandez
2025-07-20  0:14         ` 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=20250703023511.82768-1-luis.hernandez093@gmail.com \
    --to=luis.hernandez093@gmail.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=mkl@pengutronix.de \
    --cc=ondrej.ille@gmail.com \
    --cc=pisa@cmp.felk.cvut.cz \
    /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