From: "chenmiao" <chenmiao@openatom.club>
To: <miguel.ojeda.sandonis@gmail.com>, <tamird@gmail.com>,
<da.gomez@samsung.com>
Cc: <hust-os-kernel-patches@googlegroups.com>,
<linux-kernel@vger.kernel.org>, <rust-for-linux@vger.kernel.org>
Subject: [PATCH v2] Makefile: Remove the product of pin_init cleanly in mrporper
Date: Fri, 31 Oct 2025 02:32:39 +0000 [thread overview]
Message-ID: <71ff222b8731e63e06059c5d8566434e508baf2b.1761876365.git.chenmiao@openatom.club> (raw)
When I enabled Rust compilation, I wanted to clean up its output, so I
used make clean and make mrproper. However, I was still able to find that
libpin_init_internal.so in the rust directory was not deleted, while
all other corresponding outputs were cleared.
Dongliang Mu <dzm91@hust.edu.cn>
Signed-off-by: chenmiao <chenmiao@openatom.club>
---
Changes in V2:
- Add the `.dylib` to mrproper files.
---
Makefile | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index b34a1f4c03967..b38b2895e1e4a 100644
--- a/Makefile
+++ b/Makefile
@@ -1590,7 +1590,8 @@ MRPROPER_FILES += include/config include/generated \
certs/x509.genkey \
vmlinux-gdb.py \
rpmbuild \
- rust/libmacros.so rust/libmacros.dylib
+ rust/libmacros.so rust/libmacros.dylib \
+ rust/libpin_init_internal.so rust/libpin_init_internal.dylib
# clean - Delete most, but leave enough to build external modules
#
--
2.43.0
next reply other threads:[~2025-10-31 2:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 2:32 chenmiao [this message]
2025-12-17 1:54 ` Chen Miao
2026-01-18 22:30 ` Miguel Ojeda
2026-01-19 13:30 ` Chen Miao
2026-01-19 14:16 ` Benno Lossin
2026-01-20 11:13 ` Nicolas Schier
2026-01-23 10:01 ` Miguel Ojeda
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=71ff222b8731e63e06059c5d8566434e508baf2b.1761876365.git.chenmiao@openatom.club \
--to=chenmiao@openatom.club \
--cc=da.gomez@samsung.com \
--cc=hust-os-kernel-patches@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@gmail.com \
/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
all inboxes | Powered by JetHome®