From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Mao Jinlong <quic_jinlmao@quicinc.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the coresight tree
Date: Mon, 23 Jan 2023 10:59:15 +0000 [thread overview]
Message-ID: <d87ac82e-6e39-7f75-1cfc-9f96042c0fc7@arm.com> (raw)
In-Reply-To: <20230123150513.4d9cf5cd@canb.auug.org.au>
Hi Stephen
On 23/01/2023 04:05, Stephen Rothwell wrote:
> Hi all,
>
> After merging the coresight tree, today's linux-next build (htmldocs)
> produced these warnings:
>
> Documentation/trace/coresight/coresight-tpda.rst:3: WARNING: Title overline too short.
>
> ==============================
> The trace performance monitoring and diagnostics aggregator(TPDA).
> ==============================
> Documentation/trace/coresight/coresight-tpdm.rst:3: WARNING: Title overline too short.
>
> ==============================
> Trace performance monitoring and diagnostics monitor(TPDM).
> ==============================
>
> Introduced by commit
>
> 758d638667d4 ("Documentation: trace: Add documentation for TPDM and TPDA")
>
Thanks for the report, Bagas has sent a series to fix them, I will queue it.
https://lkml.kernel.org/r/20230121040015.28139-1-bagasdotme@gmail.com
Suzuki
prev parent reply other threads:[~2023-01-23 10:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 4:05 linux-next: build warnings after merge of the coresight tree Stephen Rothwell
2023-01-23 10:59 ` 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=d87ac82e-6e39-7f75-1cfc-9f96042c0fc7@arm.com \
--to=suzuki.poulose@arm.com \
--cc=bagasdotme@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=quic_jinlmao@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