From: Randy Dunlap <rdunlap@infradead.org>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Shyam Sundar S K" <Shyam-sundar.S-k@amd.com>,
"Jonathan Corbet" <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH 1/1] Docs/admin-guide: Remove pmf leftover reference from the index
Date: Mon, 15 Jul 2024 07:45:55 -0700 [thread overview]
Message-ID: <2ee554e6-944f-4a2a-afb0-50fec5d37d26@infradead.org> (raw)
In-Reply-To: <20240715104102.4615-1-ilpo.jarvinen@linux.intel.com>
On 7/15/24 3:41 AM, Ilpo Järvinen wrote:
> pmf.rst was removed by the commit 2fd66f7d3b0d ("platform/x86/amd/pmf:
> Remove update system state document") but the reference in the
> admin-guide index remained in place which triggers this warning:
>
> Documentation/admin-guide/index.rst:75: WARNING: toctree contains
> reference to nonexisting document 'admin-guide/pmf'
>
> Remove pmf also from the index to avoid the warning.
>
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
>
> I'll put this patch into pdx86/for-next that introduces the problem
> before making the PR to Linus.
>
> Documentation/admin-guide/index.rst | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/Documentation/admin-guide/index.rst b/Documentation/admin-guide/index.rst
> index 32ea52f1d150..e85b1adf5908 100644
> --- a/Documentation/admin-guide/index.rst
> +++ b/Documentation/admin-guide/index.rst
> @@ -121,7 +121,6 @@ configure specific aspects of kernel behavior to your liking.
> parport
> perf-security
> pm/index
> - pmf
> pnp
> rapidio
> RAS/index
--
~Randy
prev parent reply other threads:[~2024-07-15 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 10:41 Ilpo Järvinen
2024-07-15 14:45 ` Randy Dunlap [this message]
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=2ee554e6-944f-4a2a-afb0-50fec5d37d26@infradead.org \
--to=rdunlap@infradead.org \
--cc=Shyam-sundar.S-k@amd.com \
--cc=corbet@lwn.net \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®