From: Jasper Spaans <jasper@vs19.net>
To: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: [PATCH] typo fix
Date: Mon, 26 May 2003 13:26:45 +0200 [thread overview]
Message-ID: <20030526112645.GA15462@spaans.vs19.net> (raw)
A small documentation fix:
Index: kernel/sched.c
===================================================================
RCS file: /home/cvs/linux-2.5/kernel/sched.c,v
retrieving revision 1.175
diff -u -r1.175 sched.c
--- kernel/sched.c 19 May 2003 17:46:39 -0000 1.175
+++ kernel/sched.c 26 May 2003 10:20:14 -0000
@@ -2051,7 +2051,7 @@
}
/**
- * sys_sched_get_priority_mix - return minimum RT priority.
+ * sys_sched_get_priority_min - return minimum RT priority.
* @policy: scheduling class.
*
* this syscall returns the minimum rt_priority that can be used
Bye,
Jasper
--
Jasper Spaans
http://jsp.vs19.net/contact/
``Got no clue? Too bad for you.''
reply other threads:[~2003-05-26 11:13 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=20030526112645.GA15462@spaans.vs19.net \
--to=jasper@vs19.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®