All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,willy@infradead.org,kasong@tencent.com,akpm@linux-foundation.org
Subject: [folded-merged] lib-xarray-introduce-a-new-helper-xas_get_order-v4.patch removed from -mm tree
Date: Thu, 25 Apr 2024 20:23:18 -0700	[thread overview]
Message-ID: <20240426032319.4122DC113CD@smtp.kernel.org> (raw)


The quilt patch titled
     Subject: lib/xarray: introduce a new helper xas_get_order
has been removed from the -mm tree.  Its filename was
     lib-xarray-introduce-a-new-helper-xas_get_order-v4.patch

This patch was dropped because it was folded into lib-xarray-introduce-a-new-helper-xas_get_order.patch

------------------------------------------------------
From: Kairui Song <kasong@tencent.com>
Subject: lib/xarray: introduce a new helper xas_get_order
Date: Tue, 16 Apr 2024 15:17:21 +0800

simplify comment, sparse warning fix, per Matthew Wilcox

Link: https://lkml.kernel.org/r/20240416071722.45997-4-ryncsn@gmail.com
Signed-off-by: Kairui Song <kasong@tencent.com>
Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 lib/xarray.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

--- a/lib/xarray.c~lib-xarray-introduce-a-new-helper-xas_get_order-v4
+++ a/lib/xarray.c
@@ -1750,7 +1750,7 @@ unlock:
 EXPORT_SYMBOL(xa_store_range);
 
 /**
- * xas_get_order() - Get the order of an loaded entry after xas_load.
+ * xas_get_order() - Get the order of an entry.
  * @xas: XArray operation state.
  *
  * Called after xas_load, the xas should not be in an error state.
@@ -1769,7 +1769,7 @@ int xas_get_order(struct xa_state *xas)
 
 		if (slot >= XA_CHUNK_SIZE)
 			break;
-		if (!xa_is_sibling(xas->xa_node->slots[slot]))
+		if (!xa_is_sibling(xa_entry(xas->xa, xas->xa_node, slot)))
 			break;
 		order++;
 	}
_

Patches currently in -mm which might be from kasong@tencent.com are

mm-filemap-return-early-if-failed-to-allocate-memory-for-split.patch
mm-filemap-clean-up-hugetlb-exclusion-code.patch
lib-xarray-introduce-a-new-helper-xas_get_order.patch
mm-filemap-optimize-filemap-folio-adding.patch


                 reply	other threads:[~2024-04-26  3:23 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=20240426032319.4122DC113CD@smtp.kernel.org \
    --to=akpm@linux-foundation.org \
    --cc=kasong@tencent.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.