mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nikita Shubin via B4 Relay <devnull+n.shubin.yadro.com@kernel.org>
To: Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>,
	 Jonathan Corbet <corbet@lwn.net>
Cc: nikita.shubin@maquefel.me, linux-doc@vger.kernel.org,
	 linux-kernel@vger.kernel.org, linux@yadro.com,
	 Nikita Shubin <n.shubin@yadro.com>
Subject: [PATCH] workqueue: doc: Fix function name
Date: Fri, 19 Jul 2024 17:17:38 +0300	[thread overview]
Message-ID: <20240719-fix_doc-v1-1-9d176e38ba98@yadro.com> (raw)

From: Nikita Shubin <n.shubin@yadro.com>

s/alloc_ordered_queue()/alloc_ordered_workqueue()/

Signed-off-by: Nikita Shubin <n.shubin@yadro.com>
---
 Documentation/core-api/workqueue.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/core-api/workqueue.rst b/Documentation/core-api/workqueue.rst
index bcc370c876be..f28d7a1ab4b1 100644
--- a/Documentation/core-api/workqueue.rst
+++ b/Documentation/core-api/workqueue.rst
@@ -260,7 +260,7 @@ Some users depend on strict execution ordering where only one work item
 is in flight at any given time and the work items are processed in
 queueing order. While the combination of ``@max_active`` of 1 and
 ``WQ_UNBOUND`` used to achieve this behavior, this is no longer the
-case. Use ``alloc_ordered_queue()`` instead.
+case. Use ``alloc_ordered_workqueue()`` instead.
 
 
 Example Execution Scenarios

---
base-commit: 080402007007ca1bed8bcb103625137a5c8446c6
change-id: 20240719-fix_doc-4ecd72bf9934

Best regards,
-- 
Nikita Shubin <n.shubin@yadro.com>



             reply	other threads:[~2024-07-19 14:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-19 14:17 Nikita Shubin via B4 Relay [this message]
2024-07-19 14:24 ` Matthew Wilcox

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=20240719-fix_doc-v1-1-9d176e38ba98@yadro.com \
    --to=devnull+n.shubin.yadro.com@kernel.org \
    --cc=corbet@lwn.net \
    --cc=jiangshanlai@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@yadro.com \
    --cc=n.shubin@yadro.com \
    --cc=nikita.shubin@maquefel.me \
    --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

all inboxes | Powered by JetHome®