From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: kernel test robot <lkp@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH, REBASED 1/2] mm, treewide: Introduce NR_PAGE_ORDERS
Date: Mon, 1 Jan 2024 14:15:12 +0300 [thread overview]
Message-ID: <20240101111512.7empzyifq7kxtzk3@box> (raw)
In-Reply-To: <202312300143.DOaFj2Yb-lkp@intel.com>
On Sat, Dec 30, 2023 at 01:47:55AM +0800, kernel test robot wrote:
> All warnings (new ones prefixed by >>):
>
> >> Documentation/admin-guide/kdump/vmcoreinfo.rst:193: WARNING: Title underline too short.
Fixup for the warning:
diff --git a/Documentation/admin-guide/kdump/vmcoreinfo.rst b/Documentation/admin-guide/kdump/vmcoreinfo.rst
index 8246f94ca307..bced9e4b6e08 100644
--- a/Documentation/admin-guide/kdump/vmcoreinfo.rst
+++ b/Documentation/admin-guide/kdump/vmcoreinfo.rst
@@ -190,7 +190,7 @@ information. Makedumpfile gets the start address of the vmalloc region
from this.
(zone.free_area, NR_PAGE_ORDERS)
--------------------------------
+--------------------------------
Free areas descriptor. User-space tools use this value to iterate the
free_area ranges. NR_PAGE_ORDERS is used by the zone buddy allocator.
--
Kiryl Shutsemau / Kirill A. Shutemov
prev parent reply other threads:[~2024-01-01 11:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-28 14:47 Kirill A. Shutemov
2023-12-28 14:47 ` [PATCH, REBASED 2/2] mm, treewide: Rename MAX_ORDER to MAX_PAGE_ORDER Kirill A. Shutemov
2023-12-28 21:32 ` [PATCH, REBASED 1/2] mm, treewide: Introduce NR_PAGE_ORDERS Zi Yan
2023-12-29 17:47 ` kernel test robot
2024-01-01 11:15 ` Kirill A. Shutemov [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=20240101111512.7empzyifq7kxtzk3@box \
--to=kirill.shutemov@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=torvalds@linux-foundation.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