From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Baoquan He <bhe@redhat.com>,
linux-kernel@vger.kernel.org, catalin.marinas@arm.com
Cc: linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
corbet@lwn.net, will@kernel.org,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] arm64: add kdump.rst into index.rst
Date: Mon, 12 Jun 2023 08:14:56 +0700 [thread overview]
Message-ID: <049d6b11-d5a9-ca28-2111-7fce2d946d7f@gmail.com> (raw)
In-Reply-To: <20230611230358.13635-1-bhe@redhat.com>
On 6/12/23 06:03, Baoquan He wrote:
> Document kdump.rst was added into Documentation/arm64/, but not listed
> in Documentation/arm64/index.rst. That triggers below warning when
> executing "make htmldoc":
>
>>> Documentation/arm64/kdump.rst: WARNING: document isn't included in any toctree
>
> Fix it now.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202306110549.ynH2Juok-lkp@intel.com/
> Signed-off-by: Baoquan He <bhe@redhat.com>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
Let me add Fixes tag:
Fixes: 03dc0e05407f39 ("Documentation: add kdump.rst to present crashkernel reservation on arm64")
> ---
> Documentation/arm64/index.rst | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/arm64/index.rst b/Documentation/arm64/index.rst
> index ae21f8118830..e58391557f00 100644
> --- a/Documentation/arm64/index.rst
> +++ b/Documentation/arm64/index.rst
> @@ -15,6 +15,7 @@ ARM64 Architecture
> cpu-feature-registers
> elf_hwcaps
> hugetlbpage
> + kdump
> legacy_instructions
> memory
> memory-tagging-extension
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2023-06-12 1:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-11 23:03 [PATCH] arm64: add kdump.rst into index.rst Baoquan He
2023-06-12 1:14 ` Bagas Sanjaya [this message]
2023-06-13 17:13 ` Catalin Marinas
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=049d6b11-d5a9-ca28-2111-7fce2d946d7f@gmail.com \
--to=bagasdotme@gmail.com \
--cc=bhe@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=will@kernel.org \
/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