On 6/3/14, 4:05 PM, Alexis Berlemont wrote:
From: Jiri Olsa <[email protected]>

Fixing several sources config dependencies to allow
separate config builds.

Signed-off-by: Jiri Olsa <[email protected]>
Cc: Arnaldo Carvalho de Melo <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Ingo Molnar <[email protected]>
Cc: Paul Mackerras <[email protected]>
Cc: Corey Ashford <[email protected]>
Cc: Frederic Weisbecker <[email protected]>
Cc: Namhyung Kim <[email protected]>
Cc: Borislav Petkov <[email protected]>
Cc: Michal Marek <[email protected]>
Cc: [email protected]
Cc: Stephane Eranian <[email protected]>
---
  tools/perf/builtin-lock.c        |  4 +++-
  tools/perf/builtin-sched.c       |  2 ++
  tools/perf/perf.c                |  6 ++++++
  tools/perf/perf.h                |  2 ++
  tools/perf/ui/browsers/scripts.c |  4 ++++
  tools/perf/ui/setup.c            | 10 +++++++++-
  6 files changed, 26 insertions(+), 2 deletions(-)

diff --git a/tools/perf/builtin-lock.c b/tools/perf/builtin-lock.c
index c852c7a..b255c20 100644
--- a/tools/perf/builtin-lock.c
+++ b/tools/perf/builtin-lock.c
@@ -992,9 +992,11 @@ int cmd_lock(int argc, const char **argv, const char 
*prefix __maybe_unused)
                                usage_with_options(report_usage, 
report_options);
                }
                rc = __cmd_report(false);
+#ifdef CONFIG_BULTIN_SCRIPT
        } else if (!strcmp(argv[0], "script")) {
                /* Aliased to 'perf script' */
-               return cmd_script(argc, argv, prefix);
+               rc = cmd_script(argc, argv, prefix);
+#endif
        } else if (!strcmp(argv[0], "info")) {
                if (argc) {
                        argc = parse_options(argc, argv,

Since you are not adding builtin-cmds.h as an included file this change takes away functionality. Each patch should ensure that existing options continue to work after the change.

ditto for all of the other changes to other files.

David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to