mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Mauro Carvalho Chehab" <mchehab+huawei@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: [PATCH v2 09/13] docs: parallel-wrapper.sh: remove script
Date: Mon, 25 Aug 2025 18:30:36 +0200	[thread overview]
Message-ID: <7a2d57ae8fddcfdf0498d5dcdab09741df26d222.1756138805.git.mchehab+huawei@kernel.org> (raw)
In-Reply-To: <cover.1756138805.git.mchehab+huawei@kernel.org>

The only usage of this script was docs Makefile. Now that
it is using the new sphinx-build-wrapper, which has inside
the code from parallel-wrapper.sh, we can drop this script.

Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
---
 Documentation/sphinx/parallel-wrapper.sh | 33 ------------------------
 1 file changed, 33 deletions(-)
 delete mode 100644 Documentation/sphinx/parallel-wrapper.sh

diff --git a/Documentation/sphinx/parallel-wrapper.sh b/Documentation/sphinx/parallel-wrapper.sh
deleted file mode 100644
index e54c44ce117d..000000000000
--- a/Documentation/sphinx/parallel-wrapper.sh
+++ /dev/null
@@ -1,33 +0,0 @@
-#!/bin/sh
-# SPDX-License-Identifier: GPL-2.0+
-#
-# Figure out if we should follow a specific parallelism from the make
-# environment (as exported by scripts/jobserver-exec), or fall back to
-# the "auto" parallelism when "-jN" is not specified at the top-level
-# "make" invocation.
-
-sphinx="$1"
-shift || true
-
-parallel="$PARALLELISM"
-if [ -z "$parallel" ] ; then
-	# If no parallelism is specified at the top-level make, then
-	# fall back to the expected "-jauto" mode that the "htmldocs"
-	# target has had.
-	auto=$(perl -e 'open IN,"'"$sphinx"' --version 2>&1 |";
-			while (<IN>) {
-				if (m/([\d\.]+)/) {
-					print "auto" if ($1 >= "1.7")
-				}
-			}
-			close IN')
-	if [ -n "$auto" ] ; then
-		parallel="$auto"
-	fi
-fi
-# Only if some parallelism has been determined do we add the -jN option.
-if [ -n "$parallel" ] ; then
-	parallel="-j$parallel"
-fi
-
-exec "$sphinx" $parallel "$@"
-- 
2.51.0


  parent reply	other threads:[~2025-08-25 16:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25 16:30 [PATCH v2 00/13] Split sphinx call logic from docs Makefile Mauro Carvalho Chehab
2025-08-25 16:30 ` [PATCH v2 01/13] scripts/jobserver-exec: move the code to a class Mauro Carvalho Chehab
2025-08-25 16:30 ` [PATCH v2 02/13] scripts/jobserver-exec: move its class to the lib directory Mauro Carvalho Chehab
2025-08-25 16:30 ` [PATCH v2 03/13] scripts/jobserver-exec: add a help message Mauro Carvalho Chehab
2025-08-25 16:30 ` [PATCH v2 04/13] scripts: sphinx-pre-install: move it to tools/docs Mauro Carvalho Chehab
2025-08-25 16:30 ` [PATCH v2 05/13] tools/docs: sphinx-pre-install: move Python version handling to lib Mauro Carvalho Chehab
2025-08-25 16:30 ` [PATCH v2 06/13] tools/docs: sphinx-build-wrapper: add a wrapper for sphinx-build Mauro Carvalho Chehab
2025-08-25 16:30 ` [PATCH v2 07/13] tools/docs: sphinx-build-wrapper: add comments and blank lines Mauro Carvalho Chehab
2025-08-25 16:30 ` [PATCH v2 08/13] tools/docs: sphinx-build-wrapper: add support to run inside venv Mauro Carvalho Chehab
2025-08-25 16:30 ` Mauro Carvalho Chehab [this message]
2025-08-25 16:30 ` [PATCH v2 10/13] docs: Makefile: document latex/PDF PAPER= parameter Mauro Carvalho Chehab
2025-08-25 16:30 ` [PATCH v2 11/13] tools/docs: sphinx-build-wrapper: add an argument for LaTeX interactive mode Mauro Carvalho Chehab
2025-08-25 16:30 ` [PATCH v2 12/13] tools/docs,scripts: sphinx-*: prevent sphinx-build crashes Mauro Carvalho Chehab
2025-08-25 16:30 ` [PATCH v2 13/13] tools/docs: sphinx-build-wrapper: allow building PDF files in parallel Mauro Carvalho Chehab

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=7a2d57ae8fddcfdf0498d5dcdab09741df26d222.1756138805.git.mchehab+huawei@kernel.org \
    --to=mchehab+huawei@kernel.org \
    --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

all inboxes | Powered by JetHome®