From: Mike Rapoport <rppt@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH] Documentation: submit-checklist: add Documentation clean builds
Date: Sun, 30 Aug 2020 14:41:53 +0300 [thread overview]
Message-ID: <20200830114153.GC423750@kernel.org> (raw)
In-Reply-To: <e38b108c-afec-fd0e-ad09-b4dd5da59fd1@infradead.org>
On Sun, Aug 23, 2020 at 05:38:12PM -0700, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@infradead.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@infradead.org>
> ---
> 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 warnings/errors.
Maybe "... without new warnings/errors"?
Unfortunately we still have plenty of old ones...
> + 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.
>
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2020-08-30 11:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 0:38 [PATCH] Documentation: submit-checklist: add Documentation clean builds Randy Dunlap
2020-08-30 11:41 ` Mike Rapoport [this message]
2020-08-30 14:54 ` Randy Dunlap
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=20200830114153.GC423750@kernel.org \
--to=rppt@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.