From: Sam Ravnborg <sam@ravnborg.org>
To: linux-kernel@vger.kernel.org, mingo@redhat.com, hpa@zytor.com,
tglx@linutronix.de
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/setup] x86: use targets in the boot Makefile instead of CLEAN_FILES
Date: Thu, 12 Mar 2009 22:06:41 +0100 [thread overview]
Message-ID: <20090312210641.GC14205@uranus.ravnborg.org> (raw)
In-Reply-To: <tip-16a6791934a1077609482dd6c091aa8b4c39a834@git.kernel.org>
On Thu, Mar 12, 2009 at 08:48:28PM +0000, H. Peter Anvin wrote:
> Commit-ID: 16a6791934a1077609482dd6c091aa8b4c39a834
> Gitweb: http://git.kernel.org/tip/16a6791934a1077609482dd6c091aa8b4c39a834
> Author: H. Peter Anvin <hpa@zytor.com>
> AuthorDate: Thu, 12 Mar 2009 13:43:14 -0700
> Commit: H. Peter Anvin <hpa@zytor.com>
> CommitDate: Thu, 12 Mar 2009 13:43:14 -0700
>
> x86: use targets in the boot Makefile instead of CLEAN_FILES
>
> Impact: cleanup
>
> Instead of using CLEAN_FILES in arch/x86/Makefile, add generated files
> to targets in arch/x86/boot/Makefile, so they will get naturally
> cleaned up by "make clean".
>
> Cc: Sam Ravnborg <sam@ravnborg.org>
> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
Acked-by: Sam Ravnborg <sam@ravnborg.org>
When you are cleaning up...
archclean:
$(Q)rm -rf $(objtree)/arch/i386
$(Q)rm -rf $(objtree)/arch/x86_64
Do we need this hack now?
I recall it was some backward soon-to-be-removed hack we made right after the x86 merge.
Sam
next parent reply other threads:[~2009-03-12 21:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-16a6791934a1077609482dd6c091aa8b4c39a834@git.kernel.org>
2009-03-12 21:06 ` Sam Ravnborg [this message]
2009-03-12 23:38 ` [tip:x86/setup] x86: use targets in the boot Makefile instead of CLEAN_FILES H. Peter Anvin
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=20090312210641.GC14205@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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