The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Andrew Morton <akpm@osdl.org>,
	linuxppc64-dev <linuxppc64-dev@ozlabs.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] ppc64: Implement a vDSO and use it for signal trampoline
Date: Mon, 31 Jan 2005 20:27:13 +0100	[thread overview]
Message-ID: <20050131192713.GA16268@mars.ravnborg.org> (raw)
In-Reply-To: <1107151447.5712.81.camel@gaston>

> Index: linux-work/arch/ppc64/kernel/vdso32/Makefile
> ===================================================================
> --- /dev/null	1970-01-01 00:00:00.000000000 +0000
> +++ linux-work/arch/ppc64/kernel/vdso32/Makefile	2005-01-31 16:25:56.000000000 +1100
> @@ -0,0 +1,50 @@
> +# Choose compiler
> +#
> +# XXX FIXME: We probably want to enforce using a biarch compiler by default
> +#             and thus use (CC) with -m64, while letting the user pass a
> +#             CROSS32_COMPILE prefix if wanted. Same goes for the zImage
> +#             wrappers
> +#
> +
> +CROSS32_COMPILE ?=
> +
> +CROSS32CC		:= $(CROSS32_COMPILE)gcc
> +CROSS32AS		:= $(CROSS32_COMPILE)as
This needs to go into arch/ppc64/Makefile

> +
> +# List of files in the vdso, has to be asm only for now
> +
> +src-vdso32 = sigtramp.S gettimeofday.S datapage.S cacheflush.S

It is normal kbuild practice to list .o files.
So it would be:

obj-vdso32 := sigtramp.o gettimeofday.o datapage.o cacheflush.o
targets    := $(obj-vdso32)
obj-vdso32 := $(addprefix $(obj)/, $(obj-vdso32))

One line saved compared to below (not counting the src-vdso32 assignment
that is unused).
Also notice that ':=' uses all over. No need to use late evaluation when
no dynamic references are used ($ $@ etc.).

> +# Build rules
> +
> +obj-vdso32 := $(addsuffix .o, $(basename $(src-vdso32)))
> +targets := $(obj-vdso32) vdso32.so
> +obj-vdso32 := $(addprefix $(obj)/, $(obj-vdso32))
> +src-vdso32 := $(addprefix $(src)/, $(src-vdso32))


Same comments to the vdso64/Makefile

	Sam

  reply	other threads:[~2005-01-31 19:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-31  6:04 [PATCH] ppc64: Implement a vDSO and use it for signal trampoline Benjamin Herrenschmidt
2005-01-31 19:27 ` Sam Ravnborg [this message]
2005-01-31 23:15   ` Benjamin Herrenschmidt
2005-02-01  0:38   ` Benjamin Herrenschmidt
2005-02-01  5:41     ` Sam Ravnborg
2005-02-01  5:55       ` Benjamin Herrenschmidt

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=20050131192713.GA16268@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=akpm@osdl.org \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc64-dev@ozlabs.org \
    --cc=torvalds@osdl.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