From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "Linux Doc Mailing List" <linux-doc@vger.kernel.org>,
linux-kernel@vger.kernel.org,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Alice Ryhl" <aliceryhl@google.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>, "Trevor Gross" <tmgross@umich.edu>,
bpf@vger.kernel.org, rust-for-linux@vger.kernel.org
Subject: Re: [PATCH v2 00/14] Fix PDF doc builds on major distros
Date: Thu, 21 Aug 2025 21:43:58 +0200 [thread overview]
Message-ID: <20250821214358.7a4d8c8f@foz.lan> (raw)
In-Reply-To: <87zfbs5vka.fsf@trenco.lwn.net>
Em Thu, 21 Aug 2025 13:22:29 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:
> Mauro Carvalho Chehab <mchehab+huawei@kernel.org> writes:
>
> > Hi Jon,
> >
> > Here it is the second version of the PDF series. I opted to split one of
> > the patches in 3, to have a clearer changelog and description.
>
> OK, in the hopes of pushing through some of this stuff, I have gone
> ahead and applied this set; if things need tweaking, we can tweak in the
> coming weeks.
Thanks, very much appreciated!
Mauro
prev parent reply other threads:[~2025-08-21 19:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 8:16 [PATCH v2 00/14] Fix PDF doc builds on major distros Mauro Carvalho Chehab
2025-08-21 8:16 ` [PATCH v2 08/14] scripts: sphinx-pre-install: fix PDF build issues on Ubuntu Mauro Carvalho Chehab
2025-08-21 8:16 ` [PATCH v2 09/14] scripts: sphinx-pre-install: add missing gentoo pdf dependencies Mauro Carvalho Chehab
2025-08-21 8:16 ` [PATCH v2 12/14] scripts: sphinx-pre-install: fix pdf dependencies for Mageia 9 Mauro Carvalho Chehab
2025-08-21 8:16 ` [PATCH v2 13/14] scripts: sphinx-pre-install: fix PDF dependencies for gentoo Mauro Carvalho Chehab
2025-08-21 19:22 ` [PATCH v2 00/14] Fix PDF doc builds on major distros Jonathan Corbet
2025-08-21 19:43 ` Mauro Carvalho Chehab [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=20250821214358.7a4d8c8f@foz.lan \
--to=mchehab+huawei@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=gary@garyguo.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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).