From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH v2 5/5] doc/Makefile: turn warnings into errors
Date: Tue, 25 Feb 2020 09:07:38 -0500 [thread overview]
Message-ID: <20200225140738.GI18302@bill-the-cat> (raw)
In-Reply-To: <20200221172403.5358-6-xypron.glpk@gmx.de>
On Fri, Feb 21, 2020 at 06:24:03PM +0100, Heinrich Schuchardt wrote:
> Several patches delivered incorrect restructured text as documentation. We
> should be able to discover this in Travis CI, Gitlab CI, or Azure CI.
>
> So let us turn all build warnings into errors.
>
> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200225/c09fa54d/attachment.sig>
prev parent reply other threads:[~2020-02-25 14:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 17:23 [PATCH v2 0/5] make htmldocs in CI Heinrich Schuchardt
2020-02-21 17:23 ` [PATCH v2 1/5] doc: update doc/sphinx/kerneldoc.py Heinrich Schuchardt
2020-02-25 14:07 ` Tom Rini
2020-02-21 17:24 ` [PATCH v2 2/5] travis: build HTML docs Heinrich Schuchardt
2020-02-22 2:47 ` Bin Meng
2020-02-25 14:07 ` Tom Rini
2020-02-21 17:24 ` [PATCH v2 3/5] gitlab: build HTML documentation Heinrich Schuchardt
2020-02-25 14:07 ` Tom Rini
2020-02-21 17:24 ` [PATCH v2 4/5] azure: " Heinrich Schuchardt
2020-02-25 14:07 ` Tom Rini
2020-02-21 17:24 ` [PATCH v2 5/5] doc/Makefile: turn warnings into errors Heinrich Schuchardt
2020-02-22 2:47 ` Bin Meng
2020-02-25 14:07 ` Tom Rini [this message]
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=20200225140738.GI18302@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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