[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFLxGvy0QqoySDFwZpygHeXvQ7hG-B7z5iZq8qx3GUkFX8w2RQ@mail.gmail.com>
Date: Mon, 1 Aug 2011 00:11:08 +0200
From: richard -rw- weinberger <richard.weinberger@...il.com>
To: David Woodhouse <dwmw2@...radead.org>
Cc: Arnaud Lacombe <lacombar@...il.com>,
"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
linux-kbuild@...r.kernel.org,
user-mode-linux-devel@...ts.sourceforge.net
Subject: Re: [PATCH 1/5] um: Use __i386__ in ifdef for vsyscall exports, not SUBARCH_i386
On Sun, Jul 31, 2011 at 1:02 AM, David Woodhouse <dwmw2@...radead.org> wrote:
> Signed-off-by: David Woodhouse <David.Woodhouse@...el.com>
> ---
> arch/um/os-Linux/Makefile | 2 --
> arch/um/os-Linux/user_syms.c | 2 +-
> 2 files changed, 1 insertions(+), 3 deletions(-)
>
> diff --git a/arch/um/os-Linux/Makefile b/arch/um/os-Linux/Makefile
> index b33f4df..78658a7 100644
> --- a/arch/um/os-Linux/Makefile
> +++ b/arch/um/os-Linux/Makefile
> @@ -13,8 +13,6 @@ USER_OBJS := $(user-objs-y) aio.o elf_aux.o execvp.o file.o helper.o irq.o \
> main.o mem.o process.o registers.o sigio.o signal.o start_up.o time.o \
> tty.o tls.o uaccess.o umid.o util.o
>
> -CFLAGS_user_syms.o += -DSUBARCH_$(SUBARCH)
> -
> HAVE_AIO_ABI := $(shell [ -r /usr/include/linux/aio_abi.h ] && \
> echo -DHAVE_AIO_ABI )
> CFLAGS_aio.o += $(HAVE_AIO_ABI)
> diff --git a/arch/um/os-Linux/user_syms.c b/arch/um/os-Linux/user_syms.c
> index 45ffe46..9165513 100644
> --- a/arch/um/os-Linux/user_syms.c
> +++ b/arch/um/os-Linux/user_syms.c
> @@ -45,7 +45,7 @@ EXPORT_SYMBOL(readdir64);
> extern void truncate64(void) __attribute__((weak));
> EXPORT_SYMBOL(truncate64);
>
> -#ifdef SUBARCH_i386
> +#ifdef __i386__
> EXPORT_SYMBOL(vsyscall_ehdr);
> EXPORT_SYMBOL(vsyscall_end);
> #endif
Why do we need this?
--
Thanks,
//richard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists