public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Akira Yokosawa <akiyks@gmail.com>,
	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: Fri, 26 Sep 2025 12:19:05 +0200	[thread overview]
Message-ID: <20250926121905.385a084d@foz.lan> (raw)
In-Reply-To: <fbfb1bf8-c4b9-4c9b-9d58-84c2dda22649@infradead.org>

Em Thu, 25 Sep 2025 09:59:45 -0700
Randy Dunlap <rdunlap@infradead.org> escreveu:

> Hi Akira,
> 
> On 9/25/25 7:15 AM, Akira Yokosawa wrote:
> > 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.  
> 
> 
> Right, I don't have any texlive (or latex or tetex) packages installed.
> I shouldn't need to since I am not building any pdfdocs, so I
> shouldn't get these warning messages. But if they go away in the near
> future, that's great.

Just sent the fixes. They are because I forgot to do another cleanup
at docs Makefile and didn't test on an environment without latex.

Fix is trivial: just drop the second (unneeded) pdfdocs target.


Thanks,
Mauro

      reply	other threads:[~2025-09-26 10:19 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
2025-09-25 16:59     ` Randy Dunlap
2025-09-26 10:19       ` 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=20250926121905.385a084d@foz.lan \
    --to=mchehab+huawei@kernel.org \
    --cc=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