From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,lorenzo.stoakes@oracle.com,cheng20011202@gmail.com,akpm@linux-foundation.org
Subject: [merged mm-stable] mm-readahead-fix-typo-in-comment.patch removed from -mm tree
Date: Fri, 06 Feb 2026 15:48:08 -0800 [thread overview]
Message-ID: <20260206234809.764CEC116C6@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm/readahead: fix typo in comment
has been removed from the -mm tree. Its filename was
mm-readahead-fix-typo-in-comment.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: Wilson Zeng <cheng20011202@gmail.com>
Subject: mm/readahead: fix typo in comment
Date: Tue, 27 Jan 2026 23:25:35 +0800
Fix a typo in a comment: max_readhead -> max_readahead.
Link: https://lkml.kernel.org/r/20260127152535.321951-1-cheng20011202@gmail.com
Signed-off-by: Wilson Zeng <cheng20011202@gmail.com>
Reviewed-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/readahead.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/readahead.c~mm-readahead-fix-typo-in-comment
+++ a/mm/readahead.c
@@ -436,7 +436,7 @@ static unsigned long get_next_ra_size(st
* based on I/O request size and the max_readahead.
*
* The code ramps up the readahead size aggressively at first, but slow down as
- * it approaches max_readhead.
+ * it approaches max_readahead.
*/
static inline int ra_alloc_folio(struct readahead_control *ractl, pgoff_t index,
_
Patches currently in -mm which might be from cheng20011202@gmail.com are
reply other threads:[~2026-02-06 23:48 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=20260206234809.764CEC116C6@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=cheng20011202@gmail.com \
--cc=lorenzo.stoakes@oracle.com \
--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.