From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,hannes@cmpxchg.org,cerasuolodomenico@gmail.com,hezhongkun.hzk@bytedance.com,akpm@linux-foundation.org
Subject: [to-be-updated] mm-z3fold-remove-unneeded-spinlock.patch removed from -mm tree
Date: Wed, 21 Feb 2024 14:24:14 -0800 [thread overview]
Message-ID: <20240221222415.66B15C43390@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm/z3fold: remove unneeded spinlock
has been removed from the -mm tree. Its filename was
mm-z3fold-remove-unneeded-spinlock.patch
This patch was dropped because an updated version will be merged
------------------------------------------------------
From: Zhongkun He <hezhongkun.hzk@bytedance.com>
Subject: mm/z3fold: remove unneeded spinlock
Date: Sun, 4 Feb 2024 20:54:04 +0800
There is no need to use spinlock in this section, so remove it.
Link: https://lkml.kernel.org/r/20240204125404.2112384-1-hezhongkun.hzk@bytedance.com
Signed-off-by: Zhongkun He <hezhongkun.hzk@bytedance.com>
Cc: Domenico Cerasuolo <cerasuolodomenico@gmail.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/z3fold.c | 2 --
1 file changed, 2 deletions(-)
--- a/mm/z3fold.c~mm-z3fold-remove-unneeded-spinlock
+++ a/mm/z3fold.c
@@ -442,8 +442,6 @@ static void __release_z3fold_page(struct
WARN_ON(!list_empty(&zhdr->buddy));
set_bit(PAGE_STALE, &page->private);
clear_bit(NEEDS_COMPACTING, &page->private);
- spin_lock(&pool->lock);
- spin_unlock(&pool->lock);
if (locked)
z3fold_page_unlock(zhdr);
_
Patches currently in -mm which might be from hezhongkun.hzk@bytedance.com are
mm-z3fold-remove-unneeded-spinlock-in-z3fold_alloc.patch
mm-z3fold-fix-the-comment-for-__encode_handle.patch
reply other threads:[~2024-02-21 22:24 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=20240221222415.66B15C43390@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=cerasuolodomenico@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=hezhongkun.hzk@bytedance.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.