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>

On Fri, Jul 19, 2024 at 05:17:38PM +0300, Nikita Shubin via B4 Relay wrote:
> -case. Use ``alloc_ordered_queue()`` instead.
> +case. Use ``alloc_ordered_workqueue()`` instead.

If we remove the `` markers, this turns into a nice link to
the kernel-doc for alloc_ordered_workqueue.  ie:

+case. Use alloc_ordered_workqueue() instead.