From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,sj@kernel.org,thusharms@gmail.com,akpm@linux-foundation.org
Subject: [merged mm-stable] docs-mm-damon-design-fix-spelling-mistake.patch removed from -mm tree
Date: Mon, 12 May 2025 23:55:16 -0700 [thread overview]
Message-ID: <20250513065518.4E1BFC4CEE4@smtp.kernel.org> (raw)
The quilt patch titled
Subject: docs/mm/damon/design: fix spelling mistake
has been removed from the -mm tree. Its filename was
docs-mm-damon-design-fix-spelling-mistake.patch
This patch was dropped because it was merged into the mm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Thushara.M.S <thusharms@gmail.com>
Subject: docs/mm/damon/design: fix spelling mistake
Date: Mon May 5 02:29:12 PM PDT 2025
The word accuracy was misspelled as "accruracy".
Signed-off-by: Thushara.M.S <thusharms@gmail.com>
Reviewed-by: SeongJae Park <sj@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
Documentation/mm/damon/design.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/Documentation/mm/damon/design.rst~docs-mm-damon-design-fix-spelling-mistake
+++ a/Documentation/mm/damon/design.rst
@@ -54,7 +54,7 @@ monitoring are address-space dependent.
DAMON consolidates these implementations in a layer called DAMON Operations
Set, and defines the interface between it and the upper layer. The upper layer
is dedicated for DAMON's core logics including the mechanism for control of the
-monitoring accruracy and the overhead.
+monitoring accuracy and the overhead.
Hence, DAMON can easily be extended for any address space and/or available
hardware features by configuring the core logic to use the appropriate
_
Patches currently in -mm which might be from thusharms@gmail.com are
reply other threads:[~2025-05-13 6:55 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=20250513065518.4E1BFC4CEE4@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=mm-commits@vger.kernel.org \
--cc=sj@kernel.org \
--cc=thusharms@gmail.com \
/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.