git: 48cef9960769 - stable/15 - sched_4bsd: fix comment in maybe_preempt()

The branch stable/15 has been updated by mchoo:

URL: https://cgit.FreeBSD.org/src/commit/?id=48cef99607698b98d49722d62bb257ee575a6fab

commit 48cef99607698b98d49722d62bb257ee575a6fab
Author:     Minsoo Choo <mchoo@FreeBSD.org>
AuthorDate: 2026-08-24 02:25:36 +0000
Commit:     Minsoo Choo <mchoo@FreeBSD.org>
CommitDate: 2026-10-02 15:34:31 +0000

    sched_4bsd: fix comment in maybe_preempt()
    
    The comment says the new thread's priority is not a realtime priority
    while the code states pri > PRI_MAX_ITHD which is interrupt priorities
    not realtime.
    
    Reviewed by:    olce
    Approved by:    olce (mentor)
    MFC after:      2 weeks
    Sponsored by:   FreeBSD Foundation
    Differential Revision:  https://reviews.freebsd.org/D59402
    
    (cherry picked from commit 351f6733180cebdc83585f9a00677f4998f6c6f1)
---
 sys/kern/sched_4bsd.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sys/kern/sched_4bsd.c b/sys/kern/sched_4bsd.c
index 4db2364785f6..a77099296463 100644
--- a/sys/kern/sched_4bsd.c
+++ b/sys/kern/sched_4bsd.c
@@ -345,7 +345,7 @@ maybe_preempt(struct thread *td)
 	 *    out anyways, so there's no point in preempting.  If we did,
 	 *    the current thread would not be properly resumed as well, so
 	 *    just avoid that whole landmine.
-	 *  - If the new thread's priority is not a realtime priority and
+	 *  - If the new thread's priority is not an interrupt priority and
 	 *    the current thread's priority is not an idle priority and
 	 *    FULL_PREEMPTION is disabled.
 	 *