From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,kirill.shutemov@linux.intel.com,akpm@linux-foundation.org
Subject: [folded-merged] mm-treewide-introduce-nr_page_orders-fix.patch removed from -mm tree
Date: Sun, 07 Jan 2024 14:12:30 -0800 [thread overview]
Message-ID: <20240107221230.DF387C433C8@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm-treewide-introduce-nr_page_orders-fix
has been removed from the -mm tree. Its filename was
mm-treewide-introduce-nr_page_orders-fix.patch
This patch was dropped because it was folded into mm-treewide-introduce-nr_page_orders.patch
------------------------------------------------------
From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: mm-treewide-introduce-nr_page_orders-fix
Date: Mon, 1 Jan 2024 14:15:12 +0300
fixup for kerneldoc warning
Link: https://lkml.kernel.org/r/20240101111512.7empzyifq7kxtzk3@box
Signed-off-by: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
Documentation/admin-guide/kdump/vmcoreinfo.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/Documentation/admin-guide/kdump/vmcoreinfo.rst~mm-treewide-introduce-nr_page_orders-fix
+++ a/Documentation/admin-guide/kdump/vmcoreinfo.rst
@@ -190,7 +190,7 @@ information. Makedumpfile gets the start
from this.
(zone.free_area, NR_PAGE_ORDERS)
--------------------------------
+--------------------------------
Free areas descriptor. User-space tools use this value to iterate the
free_area ranges. MAX_ORDER is used by the zone buddy allocator.
_
Patches currently in -mm which might be from kirill.shutemov@linux.intel.com are
mm-treewide-introduce-nr_page_orders.patch
mm-treewide-rename-max_order-to-max_page_order.patch
reply other threads:[~2024-01-07 22:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240107221230.DF387C433C8@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=mm-commits@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.