public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
	Linux CoreSight <coresight@lists.linaro.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Linux Documentation <linux-doc@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Mike Leach <mike.leach@linaro.org>,
	James Clark <james.clark@arm.com>,
	Tao Zhang <quic_taozha@quicinc.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH] Documentation: ABI: coresight-tpdm: Fix Bit[3] description indentation
Date: Tue, 17 Oct 2023 11:06:17 +0100	[thread overview]
Message-ID: <44b9a917-c8e1-4166-b31a-b094eb762d2d@arm.com> (raw)
In-Reply-To: <20231017095608.136277-1-bagasdotme@gmail.com>

On 17/10/2023 10:56, Bagas Sanjaya wrote:
> Stephen Rothwell reported htmldocs warnings when merging coresight tree:
> 
> Documentation/ABI/testing/sysfs-bus-coresight-devices-tpdm:48: ERROR: Unexpected indentation.
> Documentation/ABI/testing/sysfs-bus-coresight-devices-tpdm:48: WARNING: Block quote ends without a blank line; unexpected unindent.
> 
> Fix indentation alignment for Bit[3] list entry in dsb_mode description to
> silence above warnings.
> 
> Fixes: 535d80d3c10fff ("coresight-tpdm: Add node to set dsb programming mode")
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Closes: https://lore.kernel.org/linux-next/20231017143324.75387a21@canb.auug.org.au/
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> ---
>   Documentation/ABI/testing/sysfs-bus-coresight-devices-tpdm | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/ABI/testing/sysfs-bus-coresight-devices-tpdm b/Documentation/ABI/testing/sysfs-bus-coresight-devices-tpdm
> index f07218e788439d..4dd49b159543b6 100644
> --- a/Documentation/ABI/testing/sysfs-bus-coresight-devices-tpdm
> +++ b/Documentation/ABI/testing/sysfs-bus-coresight-devices-tpdm
> @@ -54,8 +54,8 @@ Description:
>   		Accepts the value needs to be greater than 0. What data
>   		bits do is listed below.
>   		Bit[0:1] : Test mode control bit for choosing the inputs.
> -		Bit[3] : Set to 0 for low performance mode.
> -				 Set to 1 for high performance mode.
> +		Bit[3] : Set to 0 for low performance mode. Set to 1 for high
> +		performance mode.
>   		Bit[4:8] : Select byte lane for high performance mode.
>   
>   What:		/sys/bus/coresight/devices/<tpdm-name>/dsb_edge/ctrl_idx
> 
> base-commit: 90a7371cb08d7e542fa4f283c881973bba09f23b


Thanks, confirmed the patch to fix the issue. I have queued this to next.

   https://git.kernel.org/coresight/c/845333e5f0f3

Thanks
Suzuki

      reply	other threads:[~2023-10-17 10:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-17  9:56 [PATCH] Documentation: ABI: coresight-tpdm: Fix Bit[3] description indentation Bagas Sanjaya
2023-10-17 10:06 ` Suzuki K Poulose [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=44b9a917-c8e1-4166-b31a-b094eb762d2d@arm.com \
    --to=suzuki.poulose@arm.com \
    --cc=bagasdotme@gmail.com \
    --cc=coresight@lists.linaro.org \
    --cc=james.clark@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mike.leach@linaro.org \
    --cc=quic_taozha@quicinc.com \
    --cc=sfr@canb.auug.org.au \
    /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