From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,willy@infradead.org,izik.eidus@ravellosystems.com,david@redhat.com,alexs@kernel.org,akpm@linux-foundation.org
Subject: [nacked] mm-ksm-rename-mm_slot-for-get_next_rmap_item.patch removed from -mm tree
Date: Thu, 02 May 2024 08:22:29 -0700 [thread overview]
Message-ID: <20240502152230.497FFC113CC@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm/ksm: rename mm_slot for get_next_rmap_item
has been removed from the -mm tree. Its filename was
mm-ksm-rename-mm_slot-for-get_next_rmap_item.patch
This patch was dropped because it was nacked
------------------------------------------------------
From: "Alex Shi (tencent)" <alexs@kernel.org>
Subject: mm/ksm: rename mm_slot for get_next_rmap_item
Date: Sun, 28 Apr 2024 18:06:18 +0800
To distinguish ksm_mm_slot and mm_slot for better code readability, rename
parameter "struct ksm_mm_slot *mm_slot", as "struct ksm_mm_slot
*ksm_slot". No function change.
Link: https://lkml.kernel.org/r/20240428100619.3332036-4-alexs@kernel.org
Signed-off-by: Alex Shi (tencent) <alexs@kernel.org>
Cc: David Hildenbrand <david@redhat.com>
Cc: Izik Eidus <izik.eidus@ravellosystems.com>
Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/ksm.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- a/mm/ksm.c~mm-ksm-rename-mm_slot-for-get_next_rmap_item
+++ a/mm/ksm.c
@@ -2468,7 +2468,7 @@ static void cmp_and_merge_page(struct pa
}
}
-static struct ksm_rmap_item *get_next_rmap_item(struct ksm_mm_slot *mm_slot,
+static struct ksm_rmap_item *get_next_rmap_item(struct ksm_mm_slot *ksm_slot,
struct ksm_rmap_item **rmap_list,
unsigned long addr)
{
@@ -2488,7 +2488,7 @@ static struct ksm_rmap_item *get_next_rm
rmap_item = alloc_rmap_item();
if (rmap_item) {
/* It has already been zeroed */
- rmap_item->mm = mm_slot->slot.mm;
+ rmap_item->mm = ksm_slot->slot.mm;
rmap_item->mm->ksm_rmap_items++;
rmap_item->address = addr;
rmap_item->rmap_list = *rmap_list;
_
Patches currently in -mm which might be from alexs@kernel.org are
mm-ksm-add-ksm_get_folio.patch
mm-ksm-use-folio-in-remove_rmap_item_from_tree.patch
mm-ksm-add-folio_set_stable_node.patch
mm-ksm-use-folio-in-remove_stable_node.patch
mm-ksm-use-folio-in-stable_node_dup.patch
mm-ksm-use-ksm_get_folio-in-scan_get_next_rmap_item.patch
mm-ksm-use-folio-in-write_protect_page.patch
mm-ksm-convert-chain-series-funcs-and-replace-get_ksm_page.patch
mm-ksm-replace-set_page_stable_node-by-folio_set_stable_node.patch
reply other threads:[~2024-05-02 15:22 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=20240502152230.497FFC113CC@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=alexs@kernel.org \
--cc=david@redhat.com \
--cc=izik.eidus@ravellosystems.com \
--cc=mm-commits@vger.kernel.org \
--cc=willy@infradead.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.