All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Frank Li <Frank.li@nxp.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux i3c <linux-i3c@lists.infradead.org>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Miquel Raynal <miquel.raynal@bootlin.com>
Subject: Re: [PATCH] i3c: Fix i3c_device_do_priv_xfers() return value list
Date: Fri, 27 Jun 2025 06:06:26 +0700	[thread overview]
Message-ID: <3fb32ef5-055d-4885-9233-a07ddcaa5154@gmail.com> (raw)
In-Reply-To: <aF17sD+4F42RL0PL@lizhi-Precision-Tower-5810>

On 6/26/25 23:56, Frank Li wrote:
> On Thu, Jun 26, 2025 at 11:22:01AM +0700, Bagas Sanjaya wrote:
>> Sphinx reports indentation warning on i3c_device_do_priv_xfers() return
>> value list:
>>
>> Documentation/driver-api/i3c/device-driver-api:9: ./drivers/i3c/device.c:31: ERROR: Unexpected indentation. [docutils]
>>
>> Format the list as bullet list to fix the warning.
>>
>> Fixes: 0d2596508201 ("i3c: Add comment for -EAGAIN in i3c_device_do_priv_xfers()")
> 
> Needn't fixes tag here because it doesn't impact user.
> 

I found the warning on docs-next tree, though.

> subject:
> i3c: fix kernel-doc indentation of i3c_device_do_priv_xfers()
> 

Ack for the subject suggestion.

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

WARNING: multiple messages have this Message-ID (diff)
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Frank Li <Frank.li@nxp.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux i3c <linux-i3c@lists.infradead.org>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Miquel Raynal <miquel.raynal@bootlin.com>
Subject: Re: [PATCH] i3c: Fix i3c_device_do_priv_xfers() return value list
Date: Fri, 27 Jun 2025 06:06:26 +0700	[thread overview]
Message-ID: <3fb32ef5-055d-4885-9233-a07ddcaa5154@gmail.com> (raw)
In-Reply-To: <aF17sD+4F42RL0PL@lizhi-Precision-Tower-5810>

On 6/26/25 23:56, Frank Li wrote:
> On Thu, Jun 26, 2025 at 11:22:01AM +0700, Bagas Sanjaya wrote:
>> Sphinx reports indentation warning on i3c_device_do_priv_xfers() return
>> value list:
>>
>> Documentation/driver-api/i3c/device-driver-api:9: ./drivers/i3c/device.c:31: ERROR: Unexpected indentation. [docutils]
>>
>> Format the list as bullet list to fix the warning.
>>
>> Fixes: 0d2596508201 ("i3c: Add comment for -EAGAIN in i3c_device_do_priv_xfers()")
> 
> Needn't fixes tag here because it doesn't impact user.
> 

I found the warning on docs-next tree, though.

> subject:
> i3c: fix kernel-doc indentation of i3c_device_do_priv_xfers()
> 

Ack for the subject suggestion.

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

-- 
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c

  reply	other threads:[~2025-06-26 23:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-26  4:22 [PATCH] i3c: Fix i3c_device_do_priv_xfers() return value list Bagas Sanjaya
2025-06-26  4:22 ` Bagas Sanjaya
2025-06-26 16:56 ` Frank Li
2025-06-26 16:56   ` Frank Li
2025-06-26 23:06   ` Bagas Sanjaya [this message]
2025-06-26 23:06     ` Bagas Sanjaya

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=3fb32ef5-055d-4885-9233-a07ddcaa5154@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=Frank.li@nxp.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=linux-i3c@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miquel.raynal@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.