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 10/13] docs: Makefile: document latex/PDF PAPER= parameter
Date: Mon, 25 Aug 2025 18:30:37 +0200 [thread overview]
Message-ID: <565ceecafde7345153f5b7aeb1483e6cb22fec73.1756138805.git.mchehab+huawei@kernel.org> (raw)
In-Reply-To: <cover.1756138805.git.mchehab+huawei@kernel.org>
While the build system supports this for a long time, this was
never documented. Add a documentation for it.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
---
Documentation/Makefile | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/Makefile b/Documentation/Makefile
index 2b0ed8cd5ea8..3e1cb44a5fbb 100644
--- a/Documentation/Makefile
+++ b/Documentation/Makefile
@@ -124,4 +124,6 @@ dochelp:
@echo
@echo ' make DOCS_CSS={a .css file} adds a DOCS_CSS override file for html/epub output.'
@echo
+ @echo ' make PAPER={a4|letter} Specifies the paper size used for LaTeX/PDF output.'
+ @echo
@echo ' Default location for the generated documents is Documentation/output'
--
2.51.0
next prev 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 ` [PATCH v2 09/13] docs: parallel-wrapper.sh: remove script Mauro Carvalho Chehab
2025-08-25 16:30 ` Mauro Carvalho Chehab [this message]
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=565ceecafde7345153f5b7aeb1483e6cb22fec73.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®