All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,slava@dubeyko.com,idryomov@gmail.com,david@kernel.org,amarkuze@redhat.com,ziy@nvidia.com,akpm@linux-foundation.org
Subject: [merged mm-stable] ceph-replace-pageprivate-with-page_private.patch removed from -mm tree
Date: Thu, 08 Oct 2026 22:59:44 -0700	[thread overview]
Message-ID: <20261009055944.6BB411F00893@smtp.kernel.org> (raw)


The quilt patch titled
     Subject: ceph: replace PagePrivate() with page_private()
has been removed from the -mm tree.  Its filename was
     ceph-replace-pageprivate-with-page_private.patch

This patch was dropped because it was merged into the mm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm

------------------------------------------------------
From: Zi Yan <ziy@nvidia.com>
Subject: ceph: replace PagePrivate() with page_private()
Date: Sun, 20 Sep 2026 22:28:08 -0400

PagePrivate() is going to be removed along with PG_private and its
implementation is the same as page_private().

Link: https://lore.kernel.org/20260920-remove-pg_private-v5-12-bb68b6a21869@nvidia.com
Signed-off-by: Zi Yan <ziy@nvidia.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Reviewed-by: David Hildenbrand (Arm) <david@kernel.org>
Assisted-by: LLM
Cc: Ilya Dryomov <idryomov@gmail.com>
Cc: Alex Markuze <amarkuze@redhat.com>
Cc: Viacheslav Dubeyko <slava@dubeyko.com>
---

 fs/ceph/addr.c |    8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

--- a/fs/ceph/addr.c~ceph-replace-pageprivate-with-page_private
+++ a/fs/ceph/addr.c
@@ -70,9 +70,7 @@ static int ceph_netfs_check_write_begin(
 
 static inline struct ceph_snap_context *page_snap_context(struct page *page)
 {
-	if (PagePrivate(page))
-		return (void *)page->private;
-	return NULL;
+	return (void *)page_private(page);
 }
 
 /*
@@ -124,8 +122,8 @@ static bool ceph_dirty_folio(struct addr
 	spin_unlock(&ci->i_ceph_lock);
 
 	/*
-	 * Reference snap context in folio->private.  Also set
-	 * PagePrivate so that we get invalidate_folio callback.
+	 * Reference snap context in folio->private. Setting folio->private is
+	 * what gets us the invalidate_folio callback.
 	 */
 	VM_WARN_ON_FOLIO(folio->private, folio);
 	folio_attach_private(folio, snapc);
_

Patches currently in -mm which might be from ziy@nvidia.com are



                 reply	other threads:[~2026-10-09  5:59 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=20261009055944.6BB411F00893@smtp.kernel.org \
    --to=akpm@linux-foundation.org \
    --cc=amarkuze@redhat.com \
    --cc=david@kernel.org \
    --cc=idryomov@gmail.com \
    --cc=mm-commits@vger.kernel.org \
    --cc=slava@dubeyko.com \
    --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.