All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,ziy@nvidia.com,vbabka@kernel.org,
	surenb@google.com,mhocko@suse.com,hannes@cmpxchg.org,
	brendan.jackman@linux.dev,aleszlucero@gmail.com,akpm@linux-foundation.org
Subject: + mm-page_reporting-document-order-parameter-in-page_reporting_notify_free.patch added to mm-new branch
Date: Thu, 12 Nov 2026 17:45:24 -0800	[thread overview]
Message-ID: <20261113014525.736451F000C4@smtp.kernel.org> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3035 bytes --]


The patch titled
     Subject: mm/page_reporting: document @order parameter in page_reporting_notify_free()
has been added to the -mm mm-new branch.  Its filename is
     mm-page_reporting-document-order-parameter-in-page_reporting_notify_free.patch

This patch will shortly appear at
     https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/mm-page_reporting-document-order-parameter-in-page_reporting_notify_free.patch

This patch will later appear in the mm-new branch at
    git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm

Note, mm-new is a provisional staging ground for work-in-progress
patches, and acceptance into mm-new is a notification for others take
notice and to finish up reviews.  Please do not hesitate to respond to
review feedback and post updated versions to replace or incrementally
fixup patches in mm-new.

The mm-new branch of mm.git is not included in linux-next

If a few days of testing in mm-new is successful, the patch will me moved
into mm.git's mm-unstable branch, which is included in linux-next

Before you just go and hit "reply", please:
   a) Consider who else should be cc'ed
   b) Prefer to cc a suitable mailing list as well
   c) Ideally: find the original patch on the mailing list and do a
      reply-to-all to that, adding suitable additional cc's

*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***

The -mm tree is included into linux-next via various
branches at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
and is updated there most days

------------------------------------------------------
From: Oscar Alejandro Sánchez Lucero <aleszlucero@gmail.com>
Subject: mm/page_reporting: document @order parameter in page_reporting_notify_free()
Date: Thu, 12 Nov 2026 10:18:19 -0600

Add missing kernel-doc description for @order to fix a kernel-doc warning.

Link: https://lore.kernel.org/20261112-page-reporting-doc-v1-1-593af69f3801@gmail.com
Signed-off-by: Oscar Alejandro Sánchez Lucero <aleszlucero@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Cc: Vlastimil Babka <vbabka@kernel.org>
Cc: Johannes Weiner <hannes@cmpxchg.org>
Cc: Suren Baghdasaryan <surenb@google.com>
Cc: Michal Hocko <mhocko@suse.com>
Cc: Brendan Jackman <brendan.jackman@linux.dev>
Cc: Zi Yan <ziy@nvidia.com>
---

 mm/page_reporting.h |    1 +
 1 file changed, 1 insertion(+)

--- a/mm/page_reporting.h~mm-page_reporting-document-order-parameter-in-page_reporting_notify_free
+++ a/mm/page_reporting.h
@@ -23,6 +23,7 @@ static inline bool page_reported(struct
 
 /**
  * page_reporting_notify_free - Free page notification to start page processing
+ * @order: allocation order of the freed pages
  *
  * This function is meant to act as a screener for __page_reporting_notify
  * which will determine if a give zone has crossed over the high-water mark
_

Patches currently in -mm which might be from aleszlucero@gmail.com are

mm-page_reporting-document-order-parameter-in-page_reporting_notify_free.patch


                 reply	other threads:[~2026-11-13  1:45 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=20261113014525.736451F000C4@smtp.kernel.org \
    --to=akpm@linux-foundation.org \
    --cc=aleszlucero@gmail.com \
    --cc=brendan.jackman@linux.dev \
    --cc=hannes@cmpxchg.org \
    --cc=mhocko@suse.com \
    --cc=mm-commits@vger.kernel.org \
    --cc=surenb@google.com \
    --cc=vbabka@kernel.org \
    --cc=ziy@nvidia.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 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.