[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <cf5bbdf5-03ff-0606-a6d4-ca196d90aee9@infradead.org>
Date: Sun, 30 Aug 2020 17:43:54 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: LKML <linux-kernel@...r.kernel.org>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
Jonathan Corbet <corbet@....net>,
Mike Rapoport <rppt@...nel.org>
Subject: [PATCH v2] Documentation: submit-checklist: add clean builds for new
Documentation
From: Randy Dunlap <rdunlap@...radead.org>
Add to Documentation/process/submit-checklist.rst that patch
submitters should run "make htmldocs" and verify that any
Documentation/ changes (patches) are clean (no new warnings/errors).
Signed-off-by: Randy Dunlap <rdunlap@...radead.org>
Cc: Mike Rapoport <rppt@...nel.org>
---
v2: insert "new" inside "without warnings/errors" (Mike)
Documentation/process/submit-checklist.rst | 4 ++++
1 file changed, 4 insertions(+)
--- linux-next-20200821.orig/Documentation/process/submit-checklist.rst
+++ linux-next-20200821/Documentation/process/submit-checklist.rst
@@ -24,6 +24,10 @@ and elsewhere regarding submitting Linux
c) Builds successfully when using ``O=builddir``
+ d) Any Documentation/ changes build successfully without new warnings/errors.
+ Use ``make htmldocs`` or ``make pdfdocs`` to check the build and
+ fix any issues.
+
3) Builds on multiple CPU architectures by using local cross-compile tools
or some other build farm.
Powered by blists - more mailing lists