All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Linux Documentation <linux-doc@vger.kernel.org>,
	linux-next@vger.kernel.org, broonie@kernel.org
Subject: Re: docs build problems
Date: Thu, 16 Oct 2025 06:23:22 -0300	[thread overview]
Message-ID: <20251016062322.2fcd6780@sal.lan> (raw)
In-Reply-To: <87jz0v7rxe.fsf@trenco.lwn.net>

Em Wed, 15 Oct 2025 15:53:33 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:

> Mauro Carvalho Chehab <mchehab+huawei@kernel.org> writes:
> 
> > Just did a rebase. Those patches are missing:
> >
> > e2c3ba36aee2 tools/docs: sphinx-build-wrapper: -q is a boolean, not an integer
> > 0ce66e3f9c8b kernel-doc: output source file name at SEE ALSO
> > 9b34d25a58ae docs: Makefile: use PYTHONPYCACHEPREFIX
> > d5da902cc340 tools/docs: sphinx-build-wrapper: pdflatex is needed only for pdf
> > 1cad2682b785 docs: Makefile: avoid a warning when using without texlive
> > f0a4ad647aad tools/docs/sphinx-build-wrapper: allow skipping sphinx-build step
> > fb4771ad4ff4 docs: Makefile: fix rustdoc detection
> > ed7faec0095d tools/docs: sphinx-build-wrapper: fix compat with recent Tumbleweed
> > ab7dde2453af docs: conf.py: get rid of load_config.py
> > 8f421d0c327f scripts: remove sphinx-build-wrapper from scripts/
> > 9a20d16551af tools/docs: sphinx-build-wrapper: handle sphinx-build errors
> >
> > Want me to re-send them?  
> 
> *Sigh*
> 
> I forgot to pull the build-script branch back to the desktop machine
> once I got back home, so I was missing everything that I applied while
> on the road.  That has been rectified, and the needed patches are now in
> docs-next.
> 
> My apologies for the screwup.

Heh, that happens ;-)

All patches from my fixes series are there now. 

Looking at my docs pending stuff, the only thing missing is this
series:

	https://lore.kernel.org/linux-doc/cover.1759329363.git.mchehab+huawei@kernel.org/

I double-checked: it applies cleanly on the top of docs-next, as it is
unrelated to build wrapper.

Regards,
Mauro

  reply	other threads:[~2025-10-16  9:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-15 21:06 docs build problems Randy Dunlap
2025-10-15 21:15 ` Jonathan Corbet
2025-10-15 21:16   ` Randy Dunlap
2025-10-15 21:44   ` Mauro Carvalho Chehab
2025-10-15 21:47     ` Jonathan Corbet
2025-10-15 21:53     ` Jonathan Corbet
2025-10-16  9:23       ` Mauro Carvalho Chehab [this message]
2025-10-16 21:01         ` Jonathan Corbet
2025-10-17  8:26           ` 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=20251016062322.2fcd6780@sal.lan \
    --to=mchehab+huawei@kernel.org \
    --cc=broonie@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@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.