summaryrefslogtreecommitdiff
path: root/scripts
diff options
context:
space:
mode:
authorKieran Bingham <kieran@ksquared.org.uk>2016-07-14 12:06:55 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2016-07-15 14:54:27 +0900
commitabb035b48270b226356552486c6de2b1652bdb90 (patch)
tree80c1d7123e716de31c5218d84494926fe598067f /scripts
parent2ba78056acfe8d63a29565f91dae4678ed6b81ca (diff)
downloadlwn-abb035b48270b226356552486c6de2b1652bdb90.tar.gz
lwn-abb035b48270b226356552486c6de2b1652bdb90.zip
scripts/gdb: silence 'nothing to do' message
The constants.py generation, involves a rule to link into the main makefile. This rule has no command and generates a spurious warning message in the build logs when CONFIG_SCRIPTS_GDB is enabled. Fix simply by giving a no-op action Link: http://lkml.kernel.org/r/1467127337-11135-2-git-send-email-kieran@bingham.xyz Signed-off-by: Kieran Bingham <kieran@bingham.xyz> Reported-by: Jan Kiszka <jan.kiszka@siemens.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'scripts')
-rw-r--r--scripts/gdb/linux/Makefile1
1 files changed, 1 insertions, 0 deletions
diff --git a/scripts/gdb/linux/Makefile b/scripts/gdb/linux/Makefile
index cd129e65d1ff..7a33556db4e1 100644
--- a/scripts/gdb/linux/Makefile
+++ b/scripts/gdb/linux/Makefile
@@ -17,5 +17,6 @@ $(obj)/constants.py: $(SRCTREE)/$(obj)/constants.py.in
$(call if_changed,gen_constants_py)
build_constants_py: $(obj)/constants.py
+ @:
clean-files := *.pyc *.pyo $(if $(KBUILD_SRC),*.py) $(obj)/constants.py