From: Will Deacon <will@kernel.org>
To: Ilkka Koskinen <ilkka@os.amperecomputing.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the arm-perf tree
Date: Thu, 12 Oct 2023 12:31:46 +0100 [thread overview]
Message-ID: <20231012113145.GA11708@willie-the-truck> (raw)
In-Reply-To: <e8ca559b-421e-c326-f33-6edc8bfade@os.amperecomputing.com>
On Thu, Oct 12, 2023 at 01:19:41AM -0700, Ilkka Koskinen wrote:
>
> On Wed, 11 Oct 2023, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the arm-perf tree, today's linux-next build (htmldocs)
> > produced this warning:
> >
> > Documentation/admin-guide/perf/ampere_cspmu.rst: WARNING: document isn't included in any toctree
> >
> > Introduced by commit
> >
> > 53a810ad3c5c ("perf: arm_cspmu: ampere_cspmu: Add support for Ampere SoC PMU")
>
> Thanks Stephen for catching another bug!
>
>
>
> Will, it seems that I had made another stupid bug in the same patch. This
> time I hadn't added the ampere cspmu document to perf toctree. I submitted a
> fix for it:
>
> https://lore.kernel.org/all/20231012074103.3772114-1-ilkka@os.amperecomputing.com/
>
>
> Could you apply the patch or merge it with the ampere cspmu patch, whichever
> you prefer?
Cheers, I'll pick that up today.
Will
next prev parent reply other threads:[~2023-10-12 11:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 6:22 linux-next: build warning after merge of the arm-perf tree Stephen Rothwell
2023-10-12 8:19 ` Ilkka Koskinen
2023-10-12 11:31 ` Will Deacon [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-05 4:10 Stephen Rothwell
2024-03-05 12:03 ` Will Deacon
2023-06-19 4:37 Stephen Rothwell
2023-06-19 10:09 ` Will Deacon
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=20231012113145.GA11708@willie-the-truck \
--to=will@kernel.org \
--cc=ilkka@os.amperecomputing.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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