public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: cel@kernel.org
To: <kdevops@lists.linux.dev>
Cc: Daniel Gomez <da.gomez@kernel.org>, Chuck Lever <chuck.lever@oracle.com>
Subject: [RFC PATCH] refs: "make mrproper" should clean out generated refs files
Date: Wed, 12 Mar 2025 09:00:25 -0400	[thread overview]
Message-ID: <20250312130025.1403783-1-cel@kernel.org> (raw)

From: Chuck Lever <chuck.lever@oracle.com>

Doing a "make mrproper" should force the regeneration of the
default and user refs files. Otherwise these become stale because
kdevops appears to check if they exist, but not if they are newer
than the source yaml files.

Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---
 scripts/build.Makefile | 2 ++
 1 file changed, 2 insertions(+)

Simple patch, but might be controversial, so I'm posting for comments.

diff --git a/scripts/build.Makefile b/scripts/build.Makefile
index 4d3d90ab01ef..f4100bc06347 100644
--- a/scripts/build.Makefile
+++ b/scripts/build.Makefile
@@ -8,6 +8,8 @@ clean: $(clean-subdirs)
 
 PHONY += mrproper
 mrproper:
+	@$(Q)rm -rf $(CURDIR)/workflows/linux/refs/default/
+	@$(Q)rm -rf $(CURDIR)/workflows/linux/refs/user/
 	@$(Q)rm -rf $(CURDIR)/include/config/
 	@$(Q)rm -rf $(CURDIR)/include/generated/
 	@$(Q)rm -f .config
-- 
2.48.1


             reply	other threads:[~2025-03-12 13:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-12 13:00 cel [this message]
2025-03-12 15:05 ` [RFC PATCH] refs: "make mrproper" should clean out generated refs files Chuck Lever
2025-03-12 16:27   ` Daniel Gomez
2025-03-12 16:30     ` Daniel Gomez
2025-03-12 16:37       ` Daniel Gomez
2025-03-12 17:18         ` Daniel Gomez
2025-03-12 18:46           ` Chuck Lever
2025-03-13 15:12             ` Daniel Gomez

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=20250312130025.1403783-1-cel@kernel.org \
    --to=cel@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=da.gomez@kernel.org \
    --cc=kdevops@lists.linux.dev \
    /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