public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Po-Ying Chiu <charlie910417@gmail.com>
To: peterz@infradead.org
Cc: dsterba@suse.com, wqu@suse.com, mhiramat@kernel.org,
	beckerlee3@gmail.com, linux-kernel@vger.kernel.org,
	jserv@ccns.ncku.edu.tw, Po-Ying Chiu <charlie910417@gmail.com>
Subject: [PATCH] rbtree: Fix typo in header comment
Date: Sat, 12 Apr 2025 09:55:16 +0800	[thread overview]
Message-ID: <20250412015516.8924-1-charlie910417@gmail.com> (raw)

Correct "drammatically" to "dramatically" in the rbtree.h header comment.
This improves the readability of the header comment.

Signed-off-by: Po-Ying Chiu <charlie910417@gmail.com>
---
 include/linux/rbtree.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/linux/rbtree.h b/include/linux/rbtree.h
index 8d2ba3749866..78a7a260c36f 100644
--- a/include/linux/rbtree.h
+++ b/include/linux/rbtree.h
@@ -7,7 +7,7 @@
   linux/include/linux/rbtree.h
 
   To use rbtrees you'll have to implement your own insert and search cores.
-  This will avoid us to use callbacks and to drop drammatically performances.
+  This will avoid us to use callbacks and to drop dramatically performances.
   I know it's not the cleaner way,  but in C (not in C++) to get
   performances and genericity...
 

base-commit: 2eb959eeecc64fa56e9f89a5fc496da297585cbe
-- 
2.43.0


             reply	other threads:[~2025-04-12  1:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-12  1:55 Po-Ying Chiu [this message]
2025-04-14  8:43 ` [PATCH] rbtree: Fix typo in header comment David Sterba
2025-04-15 12:49   ` [PATCH v2] " Po-Ying Chiu

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=20250412015516.8924-1-charlie910417@gmail.com \
    --to=charlie910417@gmail.com \
    --cc=beckerlee3@gmail.com \
    --cc=dsterba@suse.com \
    --cc=jserv@ccns.ncku.edu.tw \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=peterz@infradead.org \
    --cc=wqu@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox