From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>,
"Darrick J. Wong" <djwong@kernel.org>,
David Chinner <david@fromorbit.com>,
linux-xfs@vger.kernel.org
Cc: Dave Chinner <dchinner@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>
Subject: linux-next: manual merge of the akpm-current tree with the xfs tree
Date: Wed, 11 Aug 2021 18:33:20 +1000 [thread overview]
Message-ID: <20210811183320.59fa209e@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1536 bytes --]
Hi all,
Today's linux-next merge of the akpm-current tree got a conflict in:
include/linux/mm.h
between commit:
de2860f46362 ("mm: Add kvrealloc()")
from the xfs tree and commit:
dcda39e2fd16 ("mm: move kvmalloc-related functions to slab.h")
from the akpm-current tree.
I fixed it up (I moved it to slab.h like the latter did with the other
functions - 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.
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Wed, 11 Aug 2021 18:30:48 +1000
Subject: [PATCH] move kvrealloc to slab.h as well
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
include/linux/slab.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/slab.h b/include/linux/slab.h
index 2c0d80cca6b8..05b8a316dc33 100644
--- a/include/linux/slab.h
+++ b/include/linux/slab.h
@@ -761,6 +761,8 @@ static inline void *kvcalloc(size_t n, size_t size, gfp_t flags)
return kvmalloc_array(n, size, flags | __GFP_ZERO);
}
+void *kvrealloc(const void *p, size_t oldsize, size_t newsize,
+ gfp_t flags);
void kvfree(const void *addr);
void kvfree_sensitive(const void *addr, size_t len);
--
2.30.2
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-08-11 8:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 8:33 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-10 7:07 Stephen Rothwell
2017-02-10 6:57 Stephen Rothwell
2017-02-10 6:45 Stephen Rothwell
2017-02-10 6:41 Stephen Rothwell
2016-02-10 5:24 Stephen Rothwell
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=20210811183320.59fa209e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-xfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®