From: "H. Peter Anvin" <hpa@zytor.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: relocs is only used with 32bit
Date: Wed, 11 Mar 2009 21:28:48 -0700 [thread overview]
Message-ID: <49B88F80.3080203@zytor.com> (raw)
In-Reply-To: <49B80F7B.2020007@kernel.org>
Hi Yinghai,
In general I prefer minimizing the conditional sections rather than
maximizing them. If nothing else, it catches errors earlier that way,
and makes it easier to eventually eliminate them entirely.
-hpa
Yinghai Lu wrote:
> Impact: cleanup
>
> those lines is not needed for 64bit
>
> Signed-off-by: Yinghai Lu <yinghai@kernel.org>
>
> ---
> arch/x86/boot/compressed/Makefile | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> Index: linux-2.6/arch/x86/boot/compressed/Makefile
> ===================================================================
> --- linux-2.6.orig/arch/x86/boot/compressed/Makefile
> +++ linux-2.6/arch/x86/boot/compressed/Makefile
> @@ -26,6 +26,7 @@ OBJCOPYFLAGS_vmlinux.bin := -R .comment
> $(obj)/vmlinux.bin: vmlinux FORCE
> $(call if_changed,objcopy)
>
> +ifeq ($(CONFIG_X86_32),y)
>
> targets += vmlinux.bin.all vmlinux.relocs relocs
> hostprogs-$(CONFIG_X86_32) += relocs
> @@ -42,8 +43,6 @@ quiet_cmd_relocbin = BUILD $@
> $(obj)/vmlinux.bin.all: $(vmlinux.bin.all-y) FORCE
> $(call if_changed,relocbin)
>
> -ifeq ($(CONFIG_X86_32),y)
> -
> ifdef CONFIG_RELOCATABLE
> $(obj)/vmlinux.bin.gz: $(obj)/vmlinux.bin.all FORCE
> $(call if_changed,gzip)
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2009-03-12 4:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 19:22 [PATCH] x86: relocs is only used with 32bit Yinghai Lu
2009-03-12 4:28 ` H. Peter Anvin [this message]
2009-03-13 22:29 ` Eric W. Biederman
2009-03-13 23:31 ` 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=49B88F80.3080203@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yinghai@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.