From: Nikita Shubin <n.shubin@xxxxxxxxx> - s/alloc_ordered_queue()/alloc_ordered_workqueue()/ - remove markers to convert it into a link. Signed-off-by: Nikita Shubin <n.shubin@xxxxxxxxx> --- Changes in v2: Matthew Wilcox: - No problem removed `` markers - Link to v1: https://lore.kernel.org/r/20240719-fix_doc-v1-1-9d176e38ba98@xxxxxxxxx --- 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..16f861c9791e 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@xxxxxxxxx>
