From: Greg Ungerer <gerg@linux-m68k.org>
To: Masahiro Yamada <masahiroy@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@lists.linux-m68k.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] m68k: add arch/m68k/Kbuild
Date: Wed, 27 May 2020 23:04:29 +1000 [thread overview]
Message-ID: <03086d60-52eb-384c-da03-11c127b7132f@linux-m68k.org> (raw)
In-Reply-To: <20200526123810.301667-1-masahiroy@kernel.org>
On 26/5/20 10:38 pm, Masahiro Yamada wrote:
> Use the standard obj-y form to specify the sub-directories under
> arch/m68k/. No functional change intended.
>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Acked-by: Greg Ungerer <gerg@linux-m68k.org>
Regards
Greg
> ---
>
> arch/m68k/Kbuild | 19 +++++++++++++++++++
> arch/m68k/Makefile | 20 +-------------------
> 2 files changed, 20 insertions(+), 19 deletions(-)
> create mode 100644 arch/m68k/Kbuild
>
> diff --git a/arch/m68k/Kbuild b/arch/m68k/Kbuild
> new file mode 100644
> index 000000000000..7dc1398dd188
> --- /dev/null
> +++ b/arch/m68k/Kbuild
> @@ -0,0 +1,19 @@
> +# SPDX-License-Identifier: GPL-2.0-only
> +obj-y += kernel/ mm/
> +obj-$(CONFIG_Q40) += q40/
> +obj-$(CONFIG_AMIGA) += amiga/
> +obj-$(CONFIG_ATARI) += atari/
> +obj-$(CONFIG_MAC) += mac/
> +obj-$(CONFIG_HP300) += hp300/
> +obj-$(CONFIG_APOLLO) += apollo/
> +obj-$(CONFIG_MVME147) += mvme147/
> +obj-$(CONFIG_MVME16x) += mvme16x/
> +obj-$(CONFIG_BVME6000) += bvme6000/
> +obj-$(CONFIG_SUN3X) += sun3x/ sun3/
> +obj-$(CONFIG_SUN3) += sun3/ sun3/prom/
> +obj-$(CONFIG_NATFEAT) += emu/
> +obj-$(CONFIG_M68040) += fpsp040/
> +obj-$(CONFIG_M68060) += ifpsp060/
> +obj-$(CONFIG_M68KFPU_EMU) += math-emu/
> +obj-$(CONFIG_M68000) += 68000/
> +obj-$(CONFIG_COLDFIRE) += coldfire/
> diff --git a/arch/m68k/Makefile b/arch/m68k/Makefile
> index 5d9288384096..88d4d8bbecd6 100644
> --- a/arch/m68k/Makefile
> +++ b/arch/m68k/Makefile
> @@ -97,27 +97,9 @@ head-$(CONFIG_SUN3) := arch/m68k/kernel/sun3-head.o
> head-$(CONFIG_M68000) := arch/m68k/68000/head.o
> head-$(CONFIG_COLDFIRE) := arch/m68k/coldfire/head.o
>
> -core-y += arch/m68k/kernel/ arch/m68k/mm/
> +core-y += arch/m68k/
> libs-y += arch/m68k/lib/
>
> -core-$(CONFIG_Q40) += arch/m68k/q40/
> -core-$(CONFIG_AMIGA) += arch/m68k/amiga/
> -core-$(CONFIG_ATARI) += arch/m68k/atari/
> -core-$(CONFIG_MAC) += arch/m68k/mac/
> -core-$(CONFIG_HP300) += arch/m68k/hp300/
> -core-$(CONFIG_APOLLO) += arch/m68k/apollo/
> -core-$(CONFIG_MVME147) += arch/m68k/mvme147/
> -core-$(CONFIG_MVME16x) += arch/m68k/mvme16x/
> -core-$(CONFIG_BVME6000) += arch/m68k/bvme6000/
> -core-$(CONFIG_SUN3X) += arch/m68k/sun3x/ arch/m68k/sun3/
> -core-$(CONFIG_SUN3) += arch/m68k/sun3/ arch/m68k/sun3/prom/
> -core-$(CONFIG_NATFEAT) += arch/m68k/emu/
> -core-$(CONFIG_M68040) += arch/m68k/fpsp040/
> -core-$(CONFIG_M68060) += arch/m68k/ifpsp060/
> -core-$(CONFIG_M68KFPU_EMU) += arch/m68k/math-emu/
> -core-$(CONFIG_M68000) += arch/m68k/68000/
> -core-$(CONFIG_COLDFIRE) += arch/m68k/coldfire/
> -
>
> all: zImage
>
>
next prev parent reply other threads:[~2020-05-27 13:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 12:38 [PATCH 1/4] m68k: add arch/m68k/Kbuild Masahiro Yamada
2020-05-26 12:38 ` [PATCH 2/4] m68k: descend to prom from arch/m68k/sun3 Masahiro Yamada
2020-06-29 17:46 ` Geert Uytterhoeven
2020-05-26 12:38 ` [PATCH 3/4] m68k: optimize cc-option calls for cpuflags-y Masahiro Yamada
2020-05-27 12:55 ` Greg Ungerer
2020-06-29 17:47 ` Geert Uytterhoeven
2020-05-26 12:38 ` [PATCH 4/4] m68k: pass -D options to KBUILD_CPPFLAGS instead of KBUILD_{A,C}FLAGS Masahiro Yamada
2020-05-27 13:00 ` Greg Ungerer
2020-06-29 17:47 ` Geert Uytterhoeven
2020-05-27 13:04 ` Greg Ungerer [this message]
2020-06-29 17:35 ` [PATCH 1/4] m68k: add arch/m68k/Kbuild Geert Uytterhoeven
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=03086d60-52eb-384c-da03-11c127b7132f@linux-m68k.org \
--to=gerg@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=masahiroy@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 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).