From: YinJie LI <liyinjie0418@gmail.com>
To: xenomai@lists.linux.dev
Subject: [PATCH] core/user-api: correct the api name
Date: Wed, 27 Sep 2023 19:09:56 +0800 [thread overview]
Message-ID: <A25826ED-41FD-4738-9D5A-C379F4E00EED@gmail.com> (raw)
Dear maintainers:
An API name correct was found in the online documentation.
Please help confirm.
Signed-off-by: Yinjie Lee <liyinjie@sinsegye.com.cn>
---
content/core/user-api/scheduling/_index.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/core/user-api/scheduling/_index.md b/content/core/user-api/scheduling/_index.md
index 00a2b62..263f3c8 100644
--- a/content/core/user-api/scheduling/_index.md
+++ b/content/core/user-api/scheduling/_index.md
@@ -13,7 +13,7 @@ module for a runnable thread in the following order:
1. [SCHED_FIFO]({{< relref "#SCHED_FIFO" >}}), which is the common
first-in, first-out real-time policy.
-2.
+2.
[SCHED_RR]({{< relref "#SCHED_RR" >}}) round-robin policy
internally.
@@ -404,7 +404,7 @@ A thread group is represented by a unique integer returned by the core
upon creation, aka the _group identifier_.
Creating a new thread group is achieved by calling
-[evl_sched_contol()]({{% relref "#evl_control_sched" %}}). Some
+[evl_control_sched()]({{% relref "#evl_control_sched" %}}). Some
information including the new group identifier is returned in the
ancillary `evl_sched_ctlinfo` structure passed to the request. The
`evl_sched_ctlparams` control structure should be filled in as
--
2.25.1
next reply other threads:[~2023-09-27 11:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 11:09 YinJie LI [this message]
2023-10-01 9:27 ` [PATCH] core/user-api: correct the api name Philippe Gerum
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=A25826ED-41FD-4738-9D5A-C379F4E00EED@gmail.com \
--to=liyinjie0418@gmail.com \
--cc=xenomai@lists.linux.dev \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).