All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,a0979652527@icloud.com,akpm@linux-foundation.org
Subject: [merged mm-nonmm-stable] lib-ratelimit-fix-spelling-mistake-seperately.patch removed from -mm tree
Date: Thu, 20 Nov 2025 14:05:00 -0800	[thread overview]
Message-ID: <20251120220500.C87D2C4CEF1@smtp.kernel.org> (raw)


The quilt patch titled
     Subject: lib: ratelimit: fix spelling mistake 'seperately'
has been removed from the -mm tree.  Its filename was
     lib-ratelimit-fix-spelling-mistake-seperately.patch

This patch was dropped because it was merged into the mm-nonmm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm

------------------------------------------------------
From: Chia-Liang Wang <a0979652527@icloud.com>
Subject: lib: ratelimit: fix spelling mistake 'seperately'
Date: Wed, 19 Nov 2025 18:11:44 +0800

Corrects a spelling mistake in a comment in ratelimit.c where 'seperately'
was used instead of 'separately'.

Link: https://lkml.kernel.org/r/20251119101144.3175-1-a0979625527@icloud.com
Signed-off-by: Chia-Liang Wang <a0979652527@icloud.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 lib/ratelimit.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/lib/ratelimit.c~lib-ratelimit-fix-spelling-mistake-seperately
+++ a/lib/ratelimit.c
@@ -27,7 +27,7 @@
 int ___ratelimit(struct ratelimit_state *rs, const char *func)
 {
 	/* Paired with WRITE_ONCE() in .proc_handler().
-	 * Changing two values seperately could be inconsistent
+	 * Changing two values separately could be inconsistent
 	 * and some message could be lost.  (See: net_ratelimit_state).
 	 */
 	int interval = READ_ONCE(rs->interval);
_

Patches currently in -mm which might be from a0979652527@icloud.com are



                 reply	other threads:[~2025-11-20 22:05 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=20251120220500.C87D2C4CEF1@smtp.kernel.org \
    --to=akpm@linux-foundation.org \
    --cc=a0979652527@icloud.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.