From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Palmer Dabbelt <palmer@dabbelt•com>
Cc: Paul Walmsley <paul@pwsan•com>, Atish Patra <atishp@rivosinc•com>,
atishp@atishpatra•org, linux-kernel@vger•kernel.org,
linux-next@vger•kernel.org
Subject: Re: linux-next: build warning after merge of the risc-v tree
Date: Fri, 1 Apr 2022 11:41:46 +1100 [thread overview]
Message-ID: <20220401114146.25ef9683@canb.auug.org.au> (raw)
In-Reply-To: <mhng-165544a6-8754-47cf-b57b-74bba73ac76b@palmer-mbp2014>
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
Hi Palmer,
On Thu, 31 Mar 2022 17:05:15 -0700 (PDT) Palmer Dabbelt <palmer@dabbelt•com> wrote:
>
> On Tue, 29 Mar 2022 09:46:57 PDT (-0700), Palmer Dabbelt wrote:
> > On Mon, 28 Mar 2022 19:34:12 PDT (-0700), Stephen Rothwell wrote:
> >>
> >> After merging the risc-v tree, today's linux-next build (htmldocs)
> >> produced this warning:
> >>
> >> Documentation/riscv/index.rst:5: WARNING: toctree contains reference to nonexisting document 'riscv/pmu'
> >>
> >> Introduced by commit
> >>
> >> 23b1f18326ec ("Documentation: riscv: Remove the old documentation")
> >>
> >> This is actually in Linus' tree. Sorry I missed it when it was
> >> introduced.
> >
> > I guess I missed it too. I just sent a patch to fix it up.
>
> Coming around to the fix reminds me that I should have asked what you're
> running to trigger these, as I should probably add it to my tests.
I just do a "make htmldocs" once a day and compare it to the previous
days results. You will need to install quite a bit of extra stuff for
sphinx to work.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-04-01 0:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 2:34 linux-next: build warning after merge of the risc-v tree Stephen Rothwell
2022-03-29 16:46 ` Palmer Dabbelt
2022-04-01 0:05 ` Palmer Dabbelt
2022-04-01 0:41 ` Stephen Rothwell [this message]
2022-04-01 3:15 ` Palmer Dabbelt
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=20220401114146.25ef9683@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=atishp@atishpatra$(echo .)org \
--cc=atishp@rivosinc$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=palmer@dabbelt$(echo .)com \
--cc=paul@pwsan$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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