From: Kieran Bingham <kieran.bingham@ideasonboard.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>,
linux-kbuild@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Michal Marek <michal.lkml@markovi.net>,
Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH 3/5] scripts/gdb: do not descend into scripts/gdb from scripts
Date: Wed, 27 Feb 2019 11:44:35 +0000 [thread overview]
Message-ID: <b7edc974-ab67-44ee-3aaa-8cac3d9bd82b@ideasonboard.com> (raw)
In-Reply-To: <1550568787-18710-3-git-send-email-yamada.masahiro@socionext.com>
Hi Yamada-san,
On 19/02/2019 09:33, Masahiro Yamada wrote:
> Currently, Kbuild descends from scripts/Makefile to scripts/gdb/Makefile
> just for creating symbolic links, but it does not need to do it so early.
>
> Merge the two descending paths to simplify the code.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> ---
>
> Makefile | 2 +-
> scripts/Makefile | 3 +--
> scripts/gdb/linux/Makefile | 9 +++------
> 3 files changed, 5 insertions(+), 9 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index 26dbcb7..a5762c6 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -1518,7 +1518,7 @@ $(DOC_TARGETS): scripts_basic FORCE
>
> PHONY += scripts_gdb
> scripts_gdb: prepare
> - $(Q)$(MAKE) $(build)=scripts/gdb/linux build_constants_py
> + $(Q)$(MAKE) $(build)=scripts/gdb
>
> ifdef CONFIG_GDB_SCRIPTS
> all: scripts_gdb
> diff --git a/scripts/Makefile b/scripts/Makefile
> index feb1f71..9d442ee 100644
> --- a/scripts/Makefile
> +++ b/scripts/Makefile
> @@ -39,7 +39,6 @@ build_unifdef: $(obj)/unifdef
> subdir-$(CONFIG_GCC_PLUGINS) += gcc-plugins
> subdir-$(CONFIG_MODVERSIONS) += genksyms
> subdir-$(CONFIG_SECURITY_SELINUX) += selinux
> -subdir-$(CONFIG_GDB_SCRIPTS) += gdb
>
> # Let clean descend into subdirs
> -subdir- += basic dtc kconfig mod package
> +subdir- += basic dtc gdb kconfig mod package
> diff --git a/scripts/gdb/linux/Makefile b/scripts/gdb/linux/Makefile
> index aba23be..7545806 100644
> --- a/scripts/gdb/linux/Makefile
> +++ b/scripts/gdb/linux/Makefile
> @@ -14,11 +14,8 @@ quiet_cmd_gen_constants_py = GEN $@
> $(CPP) -E -x c -P $(c_flags) $< > $@ ;\
> sed -i '1,/<!-- end-c-headers -->/d;' $@
>
> -targets += constants.py
> -$(obj)/constants.py: $(SRCTREE)/$(obj)/constants.py.in FORCE
> +extra-y += constants.py
> +$(obj)/constants.py: $(src)/constants.py.in FORCE
> $(call if_changed_dep,gen_constants_py)
>
> -build_constants_py: $(obj)/constants.py
> - @:
> -
> -clean-files := *.pyc *.pyo $(if $(KBUILD_SRC),*.py) $(obj)/constants.py
> +clean-files := *.pyc *.pyo $(if $(KBUILD_SRC),*.py)
This looks like the generated file will no longer be cleaned on
distclean, if the build is 'in-tree'... Is that right? Or OK if so?
Perhaps I'm mis-understanding the "$(if $(KBUILD_SRC),*.py)" statement
intent?
As long as you're content with the result, and it's understood:
Reviewed-by: Kieran Bingham <kieran.bingham@ideasonboard.com>
--
Regards
--
Kieran
next prev parent reply other threads:[~2019-02-27 11:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 9:33 [PATCH 1/5] scripts/gdb: delay generation of gdb constants.py Masahiro Yamada
2019-02-19 9:33 ` [PATCH 2/5] kbuild: remove unimportant comments from ./Kbuild Masahiro Yamada
2019-02-27 11:33 ` Kieran Bingham
2019-02-19 9:33 ` [PATCH 3/5] scripts/gdb: do not descend into scripts/gdb from scripts Masahiro Yamada
2019-02-27 11:44 ` Kieran Bingham [this message]
2019-02-27 12:38 ` Masahiro Yamada
2019-02-19 9:33 ` [PATCH 4/5] kbuild: create symlink to vmlinux-gdb.py in scripts_gdb target Masahiro Yamada
2019-02-27 11:48 ` Kieran Bingham
2019-02-19 9:33 ` [PATCH 5/5] scripts/gdb: refactor rules for symlink creation Masahiro Yamada
2019-02-27 11:55 ` Kieran Bingham
2019-02-27 12:32 ` Masahiro Yamada
2019-02-27 13:02 ` Kieran Bingham
2019-02-27 11:31 ` [PATCH 1/5] scripts/gdb: delay generation of gdb constants.py Kieran Bingham
2019-02-27 12:42 ` Masahiro Yamada
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=b7edc974-ab67-44ee-3aaa-8cac3d9bd82b@ideasonboard.com \
--to=kieran.bingham@ideasonboard.com \
--cc=jan.kiszka@siemens.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=yamada.masahiro@socionext.com \
/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
all inboxes | Powered by JetHome®