From: Akira Yokosawa <akiyks@gmail.com>
To: rdunlap@infradead.org
Cc: broonie@kernel.org, corbet@lwn.net, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
mchehab@kernel.org
Subject: Re: linux-next: Tree for Sep 24 (htmldocs / pdfdocs)
Date: Thu, 25 Sep 2025 23:15:08 +0900 [thread overview]
Message-ID: <3666a4ec-ef29-4342-b3aa-8c602c258bea@gmail.com> (raw)
In-Reply-To: <e7c29532-71de-496b-a89f-743cef28736e@infradead.org>
Hi Randy,
On Wed, 24 Sep 2025 10:54:18 -0700, Randy Dunlap wrote:
> On 9/24/25 7:41 AM, Mark Brown wrote:
>> Hi all,
>>
>> There will be no -next releases Tuesday and Wednesday next week, and
>> it's possible I might run out of time on Monday.
>>
>
> When I run 'make O=DOCS htmldocs', I see these warning messages:
>
> ../Documentation/Makefile:70: warning: overriding recipe for target 'pdfdocs'
> ../Documentation/Makefile:61: warning: ignoring old recipe for target 'pdfdocs'
>
>
> Is this a known issue?
I could reproduce these warnings under containers who have minimal
packages needed for htmldocs *only*.
Current "docs-mw" branch doesn't show them. "build-scripts" is the
one who carries this harmless regression.
By "harmless", I mean "pdfdocs" needs texlive packages anyway.
HTH,
Akira
next prev parent reply other threads:[~2025-09-25 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 14:41 linux-next: Tree for Sep 24 Mark Brown
2025-09-24 17:54 ` linux-next: Tree for Sep 24 (htmldocs / pdfdocs) Randy Dunlap
2025-09-25 14:15 ` Akira Yokosawa [this message]
2025-09-25 16:59 ` Randy Dunlap
2025-09-26 10:19 ` 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=3666a4ec-ef29-4342-b3aa-8c602c258bea@gmail.com \
--to=akiyks@gmail.com \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@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