From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Juri Lelli <juri.lelli@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-man@vger.kernel.org,
"Alejandro Colomar" <alx@kernel.org>,
"André Almeida" <andrealmeid@igalia.com>,
"Darren Hart" <dvhart@infradead.org>,
"Davidlohr Bueso" <dave@stgolabs.net>,
"Ingo Molnar" <mingo@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Valentin Schneider" <vschneid@redhat.com>,
"Waiman Long" <longman@redhat.com>
Subject: Re: [PATCH 1/4] man/man7/sched.7: Update the real-time section
Date: Mon, 8 Sep 2025 15:59:11 +0200 [thread overview]
Message-ID: <20250908135911.oX2hZuRU@linutronix.de> (raw)
In-Reply-To: <aLabrBwH4Mz8seCu@jlelli-thinkpadt14gen4.remote.csb>
On 2025-09-02 09:24:28 [+0200], Juri Lelli wrote:
> Hi!
>
> On 29/08/25 18:01, Sebastian Andrzej Siewior wrote:
>
> ...
>
> > -The FIFO and RR scheduling policies are then used to run a thread
> > +The
> > +.BR SCHED_FIFO ,
> > +.BR SCHED_RR ,
> > +and
> > +.B SCHED_DL
>
> I believe SCHED_DEADLINE would be more correct?
yes, thanks.
> Thanks,
> Juri
Sebastian
next prev parent reply other threads:[~2025-09-08 13:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 16:01 [PATCH 0/4] sched.7 and small futex.2 updates Sebastian Andrzej Siewior
2025-08-29 16:01 ` [PATCH 1/4] man/man7/sched.7: Update the real-time section Sebastian Andrzej Siewior
2025-09-02 7:24 ` Juri Lelli
2025-09-08 13:59 ` Sebastian Andrzej Siewior [this message]
2025-08-29 16:01 ` [PATCH 2/4] man/man7/sched.7: Update the documentation references Sebastian Andrzej Siewior
2025-08-30 7:28 ` G. Branden Robinson
2025-09-08 13:51 ` Sebastian Andrzej Siewior
2025-08-29 16:01 ` [PATCH 3/4] man/man2/futex.2: Recycle two gmane URLs Sebastian Andrzej Siewior
2025-08-29 16:43 ` Carlos O'Donell
2025-08-29 17:39 ` Sebastian Andrzej Siewior
2025-08-29 17:54 ` Carlos O'Donell
2025-08-31 8:48 ` Alejandro Colomar
2025-08-29 16:02 ` [PATCH 4/4] man/man2/futex.2: Add a pointer to Linux' memory-barrier Sebastian Andrzej Siewior
2025-08-29 17:46 ` Carlos O'Donell
2025-09-08 14:21 ` Sebastian Andrzej Siewior
2025-08-30 7:33 ` G. Branden Robinson
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=20250908135911.oX2hZuRU@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=alx@kernel.org \
--cc=andrealmeid@igalia.com \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=vschneid@redhat.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®