linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] A couple of patches for sphinx-build-wrapper
Date: Sun, 21 Sep 2025 16:55:46 -0600	[thread overview]
Message-ID: <87plbj8lfx.fsf@trenco.lwn.net> (raw)
In-Reply-To: <cover.1758361087.git.mchehab+huawei@kernel.org>

Mauro Carvalho Chehab <mchehab+huawei@kernel.org> writes:

> Hi Jon,
>
> This small series is against docs/build-script branch.
>
> The first patch addresses the lack of a check after running
> sphinx-build to see if it returned some error code.
>
> The second patch is a partial revert: we wneded including
> sphinx-build-wrapper twice due to a badly-solved rebase from
> my side.
>
> The third patch is a bonus cleanup: it get rids with
> load_config.py, replacing it by a single line at conf.py,
> simplifying even further docs Makefile and docs build system.
>
> Mauro Carvalho Chehab (3):
>   tools/docs: sphinx-build-wrapper: handle sphinx-build errors
>   scripts: remove sphinx-build-wrapper from scripts/
>   docs: conf.py: get rid of load_config.py

OK, I've put these onto the build-script branch.

Thanks,

jon

      parent reply	other threads:[~2025-09-21 22:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-20  9:40 [PATCH v2 0/3] A couple of patches for sphinx-build-wrapper Mauro Carvalho Chehab
2025-09-20  9:40 ` [PATCH v2 1/3] tools/docs: sphinx-build-wrapper: handle sphinx-build errors Mauro Carvalho Chehab
2025-09-20  9:40 ` [PATCH v2 2/3] scripts: remove sphinx-build-wrapper from scripts/ Mauro Carvalho Chehab
2025-09-20  9:40 ` [PATCH v2 3/3] docs: conf.py: get rid of load_config.py Mauro Carvalho Chehab
2025-09-21 22:55 ` Jonathan Corbet [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=87plbj8lfx.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@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;
as well as URLs for NNTP newsgroup(s).