From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel•org>,
Borislav Petkov <bp@alien8•de>, Tony Luck <tony.luck@intel•com>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei•com>,
Shiju Jose <shiju.jose@huawei•com>,
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 edac tree
Date: Tue, 1 Apr 2025 15:39:41 +1100 [thread overview]
Message-ID: <20250401153941.517aac17@canb.auug.org.au> (raw)
In-Reply-To: <20250228185102.15842f8b@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 493 bytes --]
Hi all,
On Fri, 28 Feb 2025 18:51:02 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> After merging the edac tree, today's linux-next build (htmldocs) produced
> this warning:
>
> Documentation/edac/index.rst: WARNING: document isn't included in any toctree
>
> Introduced by commit
>
> db99ea5f2c03 ("EDAC: Add support for EDAC device features control")
I am still getting this warning, but that commit is now in Linus' tree :-(
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-04-01 4:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 7:51 linux-next: build warning after merge of the edac tree Stephen Rothwell
2025-02-28 10:04 ` Shiju Jose
2025-02-28 10:35 ` Borislav Petkov
2025-02-28 14:44 ` Jonathan Corbet
2025-02-28 15:05 ` Borislav Petkov
2025-04-01 4:39 ` Stephen Rothwell [this message]
2025-04-01 10:44 ` Borislav Petkov
2025-04-01 12:02 ` Shiju Jose
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=20250401153941.517aac17@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=Jonathan.Cameron@huawei$(echo .)com \
--cc=bp@alien8$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mchehab+samsung@kernel$(echo .)org \
--cc=shiju.jose@huawei$(echo .)com \
--cc=tony.luck@intel$(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