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: Fri, 17 Oct 2025 05:26:36 -0300 [thread overview]
Message-ID: <20251017052636.0e5bf26d@sal.lan> (raw)
In-Reply-To: <87bjm64l4f.fsf@trenco.lwn.net>
Em Thu, 16 Oct 2025 15:01:04 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:
> Mauro Carvalho Chehab <mchehab+huawei@kernel.org> writes:
>
> > 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.
>
> In that posting, you said you weren't sure how you wanted it merged, so
> I have it just sitting in a folder. I take it you think I should pick
> it up?
Maybe the best would be to have it on a separate branch
on the top of 6.18-rc1 and have it merged to both docs and media.
This way, we'll doc build issues and prevent changes on media docs
to break things.
What do you think?
Regards,
Mauro
prev parent reply other threads:[~2025-10-17 8:26 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
2025-10-16 21:01 ` Jonathan Corbet
2025-10-17 8:26 ` 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=20251017052636.0e5bf26d@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 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).