Linux real-time development
 help / color / mirror / Atom feed
From: Zhouyi Zhou <zhouzhouyi@gmail.com>
To: bigeasy@linutronix.de, clrkwllms@kernel.org, rostedt@goodmis.org,
	david@kernel.org, akpm@linux-foundation.org, vbabka@kernel.org,
	willy@infradead.org, ljs@kernel.org, max.kellermann@ionos.com,
	linux-kernel@vger.kernel.org, linux-rt-devel@lists.linux.dev
Cc: Zhouyi Zhou <zhouzhouyi@gmail.com>
Subject: [PATCH] PREEMPT_RT: Fix the typo in the comment for kunmap_atomic()
Date: Tue,  5 May 2026 02:11:25 +0000	[thread overview]
Message-ID: <20260505021125.1941691-1-zhouzhouyi@gmail.com> (raw)

Replace `PREEMP_RT` with `PREEMPT_RT` in the header comment to
match the correct kernel configuration name.

Signed-off-by: Zhouyi Zhou <zhouzhouyi@gmail.com>

---
 include/linux/highmem-internal.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/linux/highmem-internal.h b/include/linux/highmem-internal.h
index 0574c21ca45d..bb71e7dba4f7 100644
--- a/include/linux/highmem-internal.h
+++ b/include/linux/highmem-internal.h
@@ -262,7 +262,7 @@ static inline bool is_kmap_addr(const void *x)
  * @__addr:       Virtual address to be unmapped
  *
  * Unmaps an address previously mapped by kmap_atomic() and re-enables
- * pagefaults. Depending on PREEMP_RT configuration, re-enables also
+ * pagefaults. Depending on PREEMPT_RT configuration, re-enables also
  * migration and preemption. Users should not count on these side effects.
  *
  * Mappings should be unmapped in the reverse order that they were mapped.
-- 
2.43.0


             reply	other threads:[~2026-05-05  2:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-05  2:11 Zhouyi Zhou [this message]
2026-05-05  6:46 ` [PATCH] PREEMPT_RT: Fix the typo in the comment for kunmap_atomic() Sebastian Andrzej Siewior

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=20260505021125.1941691-1-zhouzhouyi@gmail.com \
    --to=zhouzhouyi@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bigeasy@linutronix.de \
    --cc=clrkwllms@kernel.org \
    --cc=david@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-devel@lists.linux.dev \
    --cc=ljs@kernel.org \
    --cc=max.kellermann@ionos.com \
    --cc=rostedt@goodmis.org \
    --cc=vbabka@kernel.org \
    --cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox