From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, glider@google.com,
andreyknvl@google.com, akpm@linux-foundation.org,
akpm@linux-foundation.org
Subject: [folded-merged] lib-stackdepot-move-documentation-comments-to-stackdepoth-fix.patch removed from -mm tree
Date: Thu, 16 Feb 2023 18:19:24 -0800 [thread overview]
Message-ID: <20230217021925.5E205C433D2@smtp.kernel.org> (raw)
The quilt patch titled
Subject: lib-stackdepot-move-documentation-comments-to-stackdepoth-fix
has been removed from the -mm tree. Its filename was
lib-stackdepot-move-documentation-comments-to-stackdepoth-fix.patch
This patch was dropped because it was folded into lib-stackdepot-move-documentation-comments-to-stackdepoth.patch
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: lib-stackdepot-move-documentation-comments-to-stackdepoth-fix
Date: Mon Feb 13 10:04:04 AM PST 2023
grammar fix, per Alexander
Cc: Alexander Potapenko <glider@google.com>
Cc: Andrey Konovalov <andreyknvl@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
--- a/include/linux/stackdepot.h~lib-stackdepot-move-documentation-comments-to-stackdepoth-fix
+++ a/include/linux/stackdepot.h
@@ -11,7 +11,7 @@
* SLUB_DEBUG needs 256 bytes per object for that). Since allocation and free
* stack traces often repeat, using stack depot allows to save about 100x space.
*
- * Stack traces are never removed from stack depot.
+ * Stack traces are never removed from the stack depot.
*
* Author: Alexander Potapenko <glider@google.com>
* Copyright (C) 2016 Google, Inc.
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
lib-stackdepot-move-documentation-comments-to-stackdepoth.patch
mm-hugetlb-change-to-return-bool-for-isolate_hugetlb-fix.patch
mm-change-to-return-bool-for-isolate_movable_page-fix.patch
include-linux-migrateh-remove-unneeded-externs.patch
reply other threads:[~2023-02-17 2:19 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=20230217021925.5E205C433D2@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=glider@google.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.