linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jake Rice <jake@jakerice.dev>
To: corbet@lwn.net, linux-doc@vger.kernel.org
Cc: tj@kernel.org, arighi@nvidia.com, changwoo@igalia.com,
	ggherdovich@suse.com, me@mostlynerdless.de, ake@jakerice.dev,
	abovard@linux.ibm.com, devaanshk840@gmail.com, cengiz@kernel.wtf,
	linux-kernel@vger.kernel.org, Jake Rice <jake@jakerice.dev>
Subject: [PATCH] Documentation: scheduler: Changed lowercase acronyms to uppercase
Date: Tue, 13 May 2025 13:03:44 -0400	[thread overview]
Message-ID: <20250513170344.3621-1-jake@jakerice.dev> (raw)

Everywhere else in this doc, the dispatch queue acronym (DSQ) is
uppercase. There were a couple places where the acronym was written in
lowercase. I changed them to uppercase to make it homogeneous.

Signed-off-by: Jake Rice <jake@jakerice.dev>
---
 Documentation/scheduler/sched-ext.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/scheduler/sched-ext.rst b/Documentation/scheduler/sched-ext.rst
index 0b2654e2164b..878762b6379d 100644
--- a/Documentation/scheduler/sched-ext.rst
+++ b/Documentation/scheduler/sched-ext.rst
@@ -197,8 +197,8 @@ Dispatch Queues
 To match the impedance between the scheduler core and the BPF scheduler,
 sched_ext uses DSQs (dispatch queues) which can operate as both a FIFO and a
 priority queue. By default, there is one global FIFO (``SCX_DSQ_GLOBAL``),
-and one local dsq per CPU (``SCX_DSQ_LOCAL``). The BPF scheduler can manage
-an arbitrary number of dsq's using ``scx_bpf_create_dsq()`` and
+and one local DSQ per CPU (``SCX_DSQ_LOCAL``). The BPF scheduler can manage
+an arbitrary number of DSQs using ``scx_bpf_create_dsq()`` and
 ``scx_bpf_destroy_dsq()``.
 
 A CPU always executes a task from its local DSQ. A task is "inserted" into a
-- 
2.34.1


             reply	other threads:[~2025-05-13 17:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-13 17:03 Jake Rice [this message]
2025-05-13 19:20 ` [PATCH] Documentation: scheduler: Changed lowercase acronyms to uppercase Tejun Heo

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=20250513170344.3621-1-jake@jakerice.dev \
    --to=jake@jakerice.dev \
    --cc=abovard@linux.ibm.com \
    --cc=ake@jakerice.dev \
    --cc=arighi@nvidia.com \
    --cc=cengiz@kernel.wtf \
    --cc=changwoo@igalia.com \
    --cc=corbet@lwn.net \
    --cc=devaanshk840@gmail.com \
    --cc=ggherdovich@suse.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=me@mostlynerdless.de \
    --cc=tj@kernel.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;
as well as URLs for NNTP newsgroup(s).