From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,mhiramat@kernel.org,akpm@linux-foundation.org,akpm@linux-foundation.org
Subject: [folded-merged] decode_stacktrace-decode-caller-address-checkpatch-fixes.patch removed from -mm tree
Date: Tue, 24 Mar 2026 21:34:19 -0700 [thread overview]
Message-ID: <20260325043420.8AD46C4CEF7@smtp.kernel.org> (raw)
The quilt patch titled
Subject: decode_stacktrace-decode-caller-address-checkpatch-fixes
has been removed from the -mm tree. Its filename was
decode_stacktrace-decode-caller-address-checkpatch-fixes.patch
This patch was dropped because it was folded into decode_stacktrace-decode-caller-address.patch
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: decode_stacktrace-decode-caller-address-checkpatch-fixes
Date: Tue Mar 10 11:48:47 AM PDT 2026
WARNING: 'substract' may be misspelled - perhaps 'subtract'?
#106: FILE: scripts/decode_stacktrace.sh:198:
+ # symbol, substract one from that to point the call instruction.
^^^^^^^^^
Please run checkpatch prior to sending patches
Cc: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
scripts/decode_stacktrace.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/scripts/decode_stacktrace.sh~decode_stacktrace-decode-caller-address-checkpatch-fixes
+++ a/scripts/decode_stacktrace.sh
@@ -195,7 +195,7 @@ parse_symbol() {
# Evaluate it to find the actual address
# The stack trace shows the return address, which is the next
# instruction after the actual call, so as long as it's in the same
- # symbol, substract one from that to point the call instruction.
+ # symbol, subtract one from that to point the call instruction.
if [[ $decode_retaddr == false && $offset != 0 ]]; then
expr=$((expr-1))
else
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
selftests-mm-skip-uffd-wp-mremap-if-uffd-write-protect-is-unsupported-fix.patch
mm-switch-the-rmap-lock-held-option-off-in-compat-layer-fix.patch
selftests-mm-add-uffdio_move-huge-zeropage-pmd-regression-test-fix.patch
decode_stacktrace-decode-caller-address.patch
lib-list_sort-remove-dummy-cmp-calls-to-speed-up-merge_final-fix.patch
reply other threads:[~2026-03-25 4:34 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=20260325043420.8AD46C4CEF7@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=mhiramat@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.