From: Andrew Morton <akpm@linux-foundation•org>
To: Breno Leitao <leitao@debian•org>
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 mm-nonmm-unstable tree
Date: Wed, 26 Nov 2025 08:44:33 -0800 [thread overview]
Message-ID: <20251126084433.28bf7035fa56b11c5ee158d4@linux-foundation.org> (raw)
In-Reply-To: <ysfflxtpkjuv6j4evk3j3zr7ngigrcpjfvy4pqj7nuaqqsdenx@3znqkes5hrnf>
On Wed, 26 Nov 2025 05:55:36 -0800 Breno Leitao <leitao@debian•org> wrote:
> On Wed, Nov 26, 2025 at 12:55:56PM +1100, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the mm-nonmm-unstable tree, today's linux-next build
> > (htmldocs) produced this warning:
> >
> > Documentation/driver-api/hw-recoverable-errors.rst: WARNING: document isn't included in any toctree [toc.not_included]
> >
> > Introduced by commit
> >
> > c03fb5253a03 ("vmcoreinfo: track and log recoverable hardware errors")
>
> Thanks for the report, this is my fault, and I am working on it.
>
> Andrew,
>
> Do you want an additional commit or should I respin the previous one?
Either is fine, thanks. I think a little fixup is kinder to those who
have already reviewed the original patch. I'll squash such a fixup
before sending it upstream.
next prev parent reply other threads:[~2025-11-26 16:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 1:55 linux-next: build warning after merge of the mm-nonmm-unstable tree Stephen Rothwell
2025-11-26 13:55 ` Breno Leitao
2025-11-26 16:44 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-29 5:00 Stephen Rothwell
2025-07-29 9:14 ` Mike Rapoport
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=20251126084433.28bf7035fa56b11c5ee158d4@linux-foundation.org \
--to=akpm@linux-foundation$(echo .)org \
--cc=leitao@debian$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/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