From: akpm@linux-foundation.org
To: imran.f.khan@oracle.com, mm-commits@vger.kernel.org
Subject: [folded-merged] lib-stackdepot-add-helper-to-print-stack-entries-into-buffer-v3.patch removed from -mm tree
Date: Mon, 08 Nov 2021 18:14:30 -0800 [thread overview]
Message-ID: <20211109021430.yCghUmnN6%akpm@linux-foundation.org> (raw)
The patch titled
Subject: lib-stackdepot-add-helper-to-print-stack-entries-into-buffer-v3
has been removed from the -mm tree. Its filename was
lib-stackdepot-add-helper-to-print-stack-entries-into-buffer-v3.patch
This patch was dropped because it was folded into lib-stackdepot-add-helper-to-print-stack-entries-into-buffer.patch
------------------------------------------------------
From: Imran Khan <imran.f.khan@oracle.com>
Subject: lib-stackdepot-add-helper-to-print-stack-entries-into-buffer-v3
export stack_depot_snprint() to modules
Link: https://lkml.kernel.org/r/20210916133535.3592491-4-imran.f.khan@oracle.com
Signed-off-by: Imran Khan <imran.f.khan@oracle.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
lib/stackdepot.c | 1 +
1 file changed, 1 insertion(+)
--- a/lib/stackdepot.c~lib-stackdepot-add-helper-to-print-stack-entries-into-buffer-v3
+++ a/lib/stackdepot.c
@@ -236,6 +236,7 @@ int stack_depot_snprint(depot_stack_hand
return nr_entries ? stack_trace_snprint(buf, size, entries, nr_entries,
spaces) : 0;
}
+EXPORT_SYMBOL_GPL(stack_depot_snprint);
/**
* stack_depot_print - print stack entries from a depot
_
Patches currently in -mm which might be from imran.f.khan@oracle.com are
lib-stackdepot-check-stackdepot-handle-before-accessing-slabs.patch
lib-stackdepot-add-helper-to-print-stack-entries.patch
lib-stackdepot-add-helper-to-print-stack-entries-into-buffer.patch
reply other threads:[~2021-11-09 2:14 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=20211109021430.yCghUmnN6%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=imran.f.khan@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--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.