[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1467127337-11135-2-git-send-email-kieran@bingham.xyz>
Date: Tue, 28 Jun 2016 16:22:12 +0100
From: Kieran Bingham <kieran@...uared.org.uk>
To: akpm@...ux-foundation.org, corbet@....net, jan.kiszka@...mens.com,
kieran@...uared.org.uk
Cc: osandov@...com, n.borisov.lkml@...il.com,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH 1/6] 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
Reported-by: Jan Kiszka <jan.kiszka@...mens.com>
Signed-off-by: Kieran Bingham <kieran@...gham.xyz>
---
scripts/gdb/linux/Makefile | 1 +
1 file changed, 1 insertion(+)
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
--
2.7.4
Powered by blists - more mailing lists