[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20220217171210.5164c2f8@canb.auug.org.au>
Date: Thu, 17 Feb 2022 17:12:10 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Liam Howlett <liam.howlett@...cle.com>,
Mike Rapoport <rppt@...nel.org>
Cc: Karolina Drobnik <karolinadrobnik@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: linux-next: manual merge of the maple tree with the memblock tree
Hi all,
Today's linux-next merge of the maple tree got a conflict in:
tools/include/linux/slab.h
between commit:
5a198c3f9b0b ("tools: Move gfp.h and slab.h from radix-tree to lib")
from the memblock tree and commit:
3a77b4e41d4f ("radix tree test suite: Add support for slab bulk APIs")
from the maple tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
--
Cheers,
Stephen Rothwell
diff --cc tools/include/linux/slab.h
index f41d8a0eb1a4,d7aed1cc6978..000000000000
--- a/tools/include/linux/slab.h
+++ b/tools/include/linux/slab.h
@@@ -35,4 -24,8 +35,8 @@@ struct kmem_cache *kmem_cache_create(co
unsigned int align, unsigned int flags,
void (*ctor)(void *));
+ void kmem_cache_free_bulk(struct kmem_cache *cachep, size_t size, void **list);
+ int kmem_cache_alloc_bulk(struct kmem_cache *cachep, gfp_t gfp, size_t size,
+ void **list);
+
-#endif /* SLAB_H */
+#endif /* _TOOLS_SLAB_H */
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists