From: Peter Foley <pefoley2@pefoley.com>
To: Kirill Tkhai <tkhai@yandex.ru>
Cc: Michal Marek <mmarek@suse.cz>,
arnd@arndb.de, linux-kbuild@vger.kernel.org,
gregkh@linuxfoundation.org, LKML <linux-kernel@vger.kernel.org>,
oleg@redhat.com, grant.likely@secretlab.ca,
ebiederm@xmission.com, Andrew Morton <akpm@linux-foundation.org>,
ktkhai@parallels.com, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH 1/3] kbuild: Make targets names tree-wide unique on x86
Date: Sun, 14 Sep 2014 11:57:51 -0400 [thread overview]
Message-ID: <CAOFdcFP0gRDX66ius=VAN8xZZUeX9f93C7YwL52TrsJegTyy1g@mail.gmail.com> (raw)
In-Reply-To: <20140914101821.3745.21235.stgit@localhost>
On Sun, Sep 14, 2014 at 6:18 AM, Kirill Tkhai <tkhai@yandex.ru> wrote:
> diff --git a/init/Makefile b/init/Makefile
> index 7bc47ee..566a9ff 100644
> --- a/init/Makefile
> +++ b/init/Makefile
> @@ -2,23 +2,28 @@
> # Makefile for the linux kernel.
> #
>
> -obj-y := main.o version.o mounts.o
> +obj-y := main.o version.o do_mounts.o
> +
> ifneq ($(CONFIG_BLK_DEV_INITRD),y)
> obj-y += noinitramfs.o
> else
> -obj-$(CONFIG_BLK_DEV_INITRD) += initramfs.o
> +obj-y += initramfs.o do_mounts_initrd.o
> +endif
> +
> +ifeq ($(CONFIG_BLK_DEV_RAM),y)
> +obj-y += do_mounts_rd.o
> endif
> +
> +ifeq ($(CONFIG_BLK_DEV_MD),y)
> +obj-y += do_mounts_md.o
> +endif
> +
> obj-$(CONFIG_GENERIC_CALIBRATE_DELAY) += calibrate.o
>
> ifneq ($(CONFIG_ARCH_INIT_TASK),y)
> obj-y += init_task.o
> endif
>
> -mounts-y := do_mounts.o
> -mounts-$(CONFIG_BLK_DEV_RAM) += do_mounts_rd.o
> -mounts-$(CONFIG_BLK_DEV_INITRD) += do_mounts_initrd.o
> -mounts-$(CONFIG_BLK_DEV_MD) += do_mounts_md.o
> -
Can't you keep the obj-$(CONFIG_*) syntax?
e.g.
obj-$(CONFIG_BLK_DEV_RAM) += do_mounts_rd.o
next prev parent reply other threads:[~2014-09-14 15:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-14 10:18 [PATCH 0/3] Implement /proc/built-in file similar to /proc/modules Kirill Tkhai
2014-09-14 10:18 ` [PATCH 1/3] kbuild: Make targets names tree-wide unique on x86 Kirill Tkhai
2014-09-14 15:57 ` Peter Foley [this message]
2014-09-14 18:09 ` Kirill Tkhai
2014-09-14 10:18 ` [PATCH 2/3] core: Save list of built-in drivers names Kirill Tkhai
2014-09-14 10:19 ` [PATCH 3/3] core: create /proc/built-in file to show the list of built-in drivers Kirill Tkhai
2014-09-14 15:38 ` [PATCH 0/3] Implement /proc/built-in file similar to /proc/modules Greg KH
2014-09-14 17:27 ` Oleg Nesterov
2014-09-14 17:57 ` Kirill Tkhai
2014-09-14 18:12 ` Richard Weinberger
2014-09-14 18:58 ` Kirill Tkhai
2014-09-14 20:00 ` Oleg Nesterov
2014-09-14 17:31 ` Kirill Tkhai
2014-09-14 17:39 ` Greg KH
2014-09-14 18:05 ` Kirill Tkhai
2014-09-14 18:13 ` Greg KH
2014-09-14 18:35 ` Kirill Tkhai
2014-09-14 18:56 ` Greg KH
2014-09-15 11:50 ` Kirill Tkhai
2014-09-16 15:40 ` Lucas De Marchi
2014-09-15 9:17 ` Michal Marek
2014-09-15 9:12 ` Michal Marek
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='CAOFdcFP0gRDX66ius=VAN8xZZUeX9f93C7YwL52TrsJegTyy1g@mail.gmail.com' \
--to=pefoley2@pefoley.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=ebiederm@xmission.com \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@linuxfoundation.org \
--cc=ktkhai@parallels.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=oleg@redhat.com \
--cc=sam@ravnborg.org \
--cc=tkhai@yandex.ru \
/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;
as well as URLs for NNTP newsgroup(s).