The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Luis Augenstein <luis.augenstein@tngtech.com>
Cc: nsc@kernel.org, linux-kbuild@vger.kernel.org,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	gregkh@linuxfoundation.org, kstewart@linuxfoundation.org,
	maximilian.huber@tngtech.com
Subject: Re: [PATCH 1/1] kbuild: record real-prereqs in .cmd files
Date: Mon, 24 Aug 2026 23:22:42 -0400	[thread overview]
Message-ID: <20260825032242.GA1218443@ax162> (raw)
In-Reply-To: <1efb52b4-1a78-4c4e-aea1-6c8b426a8538@tngtech.com>

On Fri, Aug 21, 2026 at 09:57:03PM +0200, Luis Augenstein wrote:
> True, some Make prerequisites also appear in deps_*, so the filter
> dropped them from make_prereqs_* on incremental builds.
> 
> However, we cannot just remove the filter. After the .cmd is included,
> $(real-prereqs) contains $(deps_$@), so the whole deps_* list would
> show up in make_prereqs_* on a rebuild.

Ah, makes sense.

> We could move the filter into fixdep and filter based on the new .d file, so
> the overlap is removed already on a clean build.

If this is not that complicated, I would not mind seeing what it looked
like.

-- 
Cheers,
Nathan

      reply	other threads:[~2026-08-25  3:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-14 11:21 [PATCH 0/1] kbuild: record real-prereqs in .cmd files Luis Augenstein
2026-08-14 11:21 ` [PATCH 1/1] " Luis Augenstein
2026-08-18 19:51   ` Nathan Chancellor
2026-08-21 19:57     ` Luis Augenstein
2026-08-25  3:22       ` Nathan Chancellor [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=20260825032242.GA1218443@ax162 \
    --to=nathan@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kstewart@linuxfoundation.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luis.augenstein@tngtech.com \
    --cc=maximilian.huber@tngtech.com \
    --cc=nsc@kernel.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