Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Magnus Damm <damm@opensource.se>
To: linux-arm-kernel@lists.infradead.org
Cc: catalin.marinas@arm.com, Magnus Damm <damm@opensource.se>,
	will@kernel.org, geert+renesas@glider.be
Subject: [PATCH] arm64: clean up vdso and vdso32 files
Date: Sun, 20 Jun 2021 09:18:05 +0900	[thread overview]
Message-ID: <162414828517.22205.15691327042917921585.sendpatchset@octo> (raw)

From: Magnus Damm <damm+renesas@opensource.se>

Adjust the Makefile to remove vdso and vdso32 files during distclean.

The following vdso files get generated by the defconfig as of v5.13-rc5:
 arch/arm64/kernel/vdso/vdso.lds
 arch/arm64/kernel/vdso/vdso.so
 arch/arm64/kernel/vdso/vdso.so.dbg

Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
---

 arch/arm64/Makefile |    3 +++
 1 file changed, 3 insertions(+)

--- 0001/arch/arm64/Makefile
+++ work/arch/arm64/Makefile	2021-06-19 18:45:17.718559303 +0900
@@ -181,6 +181,9 @@ archprepare:
 # We use MRPROPER_FILES and CLEAN_FILES now
 archclean:
 	$(Q)$(MAKE) $(clean)=$(boot)
+	$(Q)$(MAKE) $(clean)=arch/arm64/kernel/vdso
+	$(if $(CONFIG_COMPAT_VDSO), \
+		$(Q)$(MAKE) $(clean)=arch/arm64/kernel/vdso32)
 
 ifeq ($(KBUILD_EXTMOD),)
 # We need to generate vdso-offsets.h before compiling certain files in kernel/.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2021-06-20  1:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-20  0:18 Magnus Damm [this message]
2021-06-21  7:43 ` [PATCH] arm64: clean up vdso and vdso32 files Geert Uytterhoeven
2021-06-21 10:55 ` Will Deacon

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=162414828517.22205.15691327042917921585.sendpatchset@octo \
    --to=damm@opensource.se \
    --cc=catalin.marinas@arm.com \
    --cc=geert+renesas@glider.be \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=will@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