From: Andrew Morton <akpm@linux-foundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
mm-commits@vger.kernel.org
Subject: [GIT PULL] Final MM updates for 6.2-rc1
Date: Sat, 17 Dec 2022 20:30:48 -0800 [thread overview]
Message-ID: <20221217203048.c502a0c0ba87b5be1bfb7824@linux-foundation.org> (raw)
Linus, please merge this handful of leftovers.
Thanks.
The following changes since commit 8fa590bf344816c925810331eea8387627bbeb40:
Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm (2022-12-15 11:12:21 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm tags/mm-stable-2022-12-17-2
for you to fetch changes up to 8b777594d2341a82f00b57c020f8af05bded1178:
MAINTAINERS: zram: zsmalloc: Add an additional co-maintainer (2022-12-15 16:37:49 -0800)
----------------------------------------------------------------
- A few late-breaking minor fixups
- Two minor feature patches which were awkwardly dependent on mm-nonmm.
I need to set up a new branch to handle such things.
----------------------------------------------------------------
Clément Léger (1):
mm/kmemleak: use %pK to display kernel pointers in backtrace
David Hildenbrand (1):
mm/gup_test: free memory allocated via kvcalloc() using kvfree()
Liam Howlett (2):
maple_tree: fix mas_find_rev() comment
maple_tree: update copyright dates for test code
Minchan Kim (1):
MAINTAINERS: zram: zsmalloc: Add an additional co-maintainer
Zhaoyang Huang (1):
mm: use stack_depot for recording kmemleak's backtrace
CREDITS | 4 ++++
MAINTAINERS | 6 ++---
lib/Kconfig.debug | 1 +
lib/maple_tree.c | 2 +-
mm/gup_test.c | 4 ++--
mm/kmemleak.c | 48 ++++++++++++++++++++++++----------------
tools/testing/radix-tree/maple.c | 5 +++--
7 files changed, 42 insertions(+), 28 deletions(-)
next reply other threads:[~2022-12-18 4:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-18 4:30 Andrew Morton [this message]
2022-12-19 14:30 ` pr-tracker-bot
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=20221217203048.c502a0c0ba87b5be1bfb7824@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mm-commits@vger.kernel.org \
--cc=torvalds@linux-foundation.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