public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shiju Jose <shiju.jose@huawei.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	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>,
	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: Fri, 28 Feb 2025 10:04:57 +0000	[thread overview]
Message-ID: <af3e1e183b034ea89ed6582a5382e5c3@huawei.com> (raw)
In-Reply-To: <20250228185102.15842f8b@canb.auug.org.au>

>-----Original Message-----
>From: Stephen Rothwell <sfr@canb.auug.org.au>
>Sent: 28 February 2025 07:51
>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: linux-next: build warning after merge of the edac tree
>
>Hi all,
>
>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")

Thanks Stephen for reporting this warning.

Hi All,

Following change fix this warning.

diff --git a/Documentation/subsystem-apis.rst b/Documentation/subsystem-apis.rst
index b52ad5b969d4..ff4fe8c936c8 100644
--- a/Documentation/subsystem-apis.rst
+++ b/Documentation/subsystem-apis.rst
@@ -71,6 +71,7 @@ Other subsystems
 
    accounting/index
    cpu-freq/index
+   edac/index
    fpga/index
    i2c/index
    iio/index 
>
>--
>Cheers,
>Stephen Rothwell

Thanks,
Shiju

  reply	other threads:[~2025-02-28 10:05 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 [this message]
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
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=af3e1e183b034ea89ed6582a5382e5c3@huawei.com \
    --to=shiju.jose@huawei.com \
    --cc=bp@alien8.de \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mchehab+samsung@kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tony.luck@intel.com \
    /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