public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zhu Jun <zhujun2@cmss.chinamobile.com>
To: corbet@lwn.net
Cc: andrea.righi@linux.dev, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, zhujun2@cmss.chinamobile.com
Subject: [PATCH] sched_ext: Documentation: Fix typo in sched-ext.rst
Date: Sun, 17 Nov 2024 18:48:18 -0800	[thread overview]
Message-ID: <20241118024818.11590-1-zhujun2@cmss.chinamobile.com> (raw)

The word 'tranfers' is wrong, so fix it.

Signed-off-by: Zhu Jun <zhujun2@cmss.chinamobile.com>
---
 Documentation/scheduler/sched-ext.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/scheduler/sched-ext.rst b/Documentation/scheduler/sched-ext.rst
index 7b59bbd2e564..aff1304d2637 100644
--- a/Documentation/scheduler/sched-ext.rst
+++ b/Documentation/scheduler/sched-ext.rst
@@ -265,7 +265,7 @@ The following briefly shows how a waking task is scheduled and executed.
      rather than performing them immediately. There can be up to
      ``ops.dispatch_max_batch`` pending tasks.
 
-   * ``scx_bpf_consume()`` tranfers a task from the specified non-local DSQ
+   * ``scx_bpf_consume()`` transfer a task from the specified non-local DSQ
      to the dispatching DSQ. This function cannot be called with any BPF
      locks held. ``scx_bpf_consume()`` flushes the pending dispatched tasks
      before trying to consume the specified DSQ.
-- 
2.17.1




             reply	other threads:[~2024-11-18  2:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-18  2:48 Zhu Jun [this message]
2024-11-20  9:36 ` [PATCH] sched_ext: Documentation: Fix typo in sched-ext.rst Andrea Righi

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=20241118024818.11590-1-zhujun2@cmss.chinamobile.com \
    --to=zhujun2@cmss.chinamobile.com \
    --cc=andrea.righi@linux.dev \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.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