1. 16 3月, 2013 1 次提交
  2. 19 2月, 2013 1 次提交
  3. 09 2月, 2013 1 次提交
  4. 01 2月, 2013 1 次提交
  5. 26 1月, 2013 1 次提交
  6. 23 1月, 2013 1 次提交
  7. 18 1月, 2013 1 次提交
  8. 10 1月, 2013 1 次提交
  9. 03 1月, 2013 1 次提交
  10. 22 12月, 2012 1 次提交
  11. 21 12月, 2012 1 次提交
    • D
      x86: Default to ARCH=x86 to avoid overriding CONFIG_64BIT · ffee0de4
      David Woodhouse 提交于
      It is easy to waste a bunch of time when one takes a 32-bit .config
      from a test machine and try to build it on a faster 64-bit system, and
      its existing setting of CONFIG_64BIT=n gets *changed* to match the
      build host.  Similarly, if one has an existing build tree it is easy
      to trash an entire build tree that way.
      
      This is because the default setting for $ARCH when discovered from
      'uname' is one of the legacy pre-x86-merge values (i386 or x86_64),
      which effectively force the setting of CONFIG_64BIT to match. We should
      default to ARCH=x86 instead, finally completing the merge that we
      started so long ago.
      
      This patch preserves the behaviour of the legacy ARCH settings for commands
      such as:
      
         make ARCH=x86_64 randconfig
         make ARCH=i386 randconfig
      
      ... since making the value of CONFIG_64BIT actually random in that situation
      is not desirable.
      
      In time, perhaps we can retire this legacy use of the old ARCH= values.
      We already have a way to override values for *any* config option, using
      $KCONFIG_ALLCONFIG, so it could be argued that we don't necessarily need
      to keep ARCH={i386,x86_64} around as a special case just for overriding
      CONFIG_64BIT.
      
      We'd probably at least want to add a way to override config options from
      the command line ('make CONFIG_FOO=y oldconfig') before we talk about doing
      that though.
      Signed-off-by: NDavid Woodhouse <David.Woodhouse@intel.com>
      Link: http://lkml.kernel.org/r/1356040315.3198.51.camel@shinybook.infradead.orgSigned-off-by: NH. Peter Anvin <hpa@linux.intel.com>
      ffee0de4
  12. 14 12月, 2012 1 次提交
    • J
      MODSIGN: Add modules_sign make target · d890f510
      Josh Boyer 提交于
      If CONFIG_MODULE_SIG is set, and 'make modules_sign' is called then this
      patch will cause the modules to get a signature appended.  The make target
      is intended to be run after 'make modules_install', and will modify the
      modules in-place in the installed location.  It can be used to produce
      signed modules after they have been processed by distribution build
      scripts.
      Signed-off-by: NJosh Boyer <jwboyer@redhat.com>
      Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (minor typo fix)
      d890f510
  13. 11 12月, 2012 1 次提交
  14. 09 12月, 2012 1 次提交
  15. 04 12月, 2012 1 次提交
  16. 26 11月, 2012 1 次提交
  17. 20 11月, 2012 2 次提交
    • C
      kbuild: Remove reference to uninitialised variable · 16f89098
      Charles Keepax 提交于
      Verbose output variable is unnecessary because the command's echo is
      already surpressed. Additionally because the block defines skip-makefile
      the variable Q is not defined within the makefile, which can cause
      problems if Q is defined in the users environment.
      Signed-off-by: NCharles Keepax <ckeepax@opensource.wolfsonmicro.com>
      Signed-off-by: NMichal Marek <mmarek@suse.cz>
      16f89098
    • D
      tools: Honour the O= flag when tool build called from a higher Makefile · bf35182f
      David Howells 提交于
      Honour the O= flag that was passed to a higher level Makefile and then passed
      down as part of a tool build.
      
      To make this work, the top-level Makefile passes the original O= flag and
      subdir=tools to the tools/Makefile, and that in turn passes
      subdir=$(O)/$(subdir)/foodir when building tool foo in directory
      $(O)/$(subdir)/foodir (where the intervening slashes aren't added if an
      element is missing).
      
      For example, take perf.  This is found in tools/perf/.  Assume we're building
      into directory ~/zebra/, so we pass O=~/zebra to make.  Dependening on where
      we run the build from, we see:
      
      	make run in dir		$(OUTPUT) dir
      	=======================	==================
      	linux			~/zebra/tools/perf/
      	linux/tools		~/zebra/perf/
      	linux/tools/perf	~/zebra/
      
      and if O= is not set, we get:
      
      	make run in dir		$(OUTPUT) dir
      	=======================	==================
      	linux			linux/tools/perf/
      	linux/tools		linux/tools/perf/
      	linux/tools/perf	linux/tools/perf/
      
      The output directories are created by the descend function if they don't
      already exist.
      Signed-off-by: NDavid Howells <dhowells@redhat.com>
      Cc: Borislav Petkov <bp@amd64.org>
      Cc: Ingo Molnar <mingo@kernel.org>
      Cc: Linus Torvalds <torvalds@linux-foundation.org>
      Cc: Namhyung Kim <namhyung@gmail.com>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Link: http://lkml.kernel.org/r/1378.1352379110@warthog.procyon.org.ukSigned-off-by: NArnaldo Carvalho de Melo <acme@redhat.com>
      bf35182f
  18. 17 11月, 2012 1 次提交
  19. 15 11月, 2012 1 次提交
    • D
      tools: Honour the O= flag when tool build called from a higher Makefile · 9db48cd5
      David Howells 提交于
      Honour the O= flag that was passed to a higher level Makefile and then passed
      down as part of a tool build.
      
      To make this work, the top-level Makefile passes the original O= flag and
      subdir=tools to the tools/Makefile, and that in turn passes
      subdir=$(O)/$(subdir)/foodir when building tool foo in directory
      $(O)/$(subdir)/foodir (where the intervening slashes aren't added if an
      element is missing).
      
      For example, take perf.  This is found in tools/perf/.  Assume we're building
      into directory ~/zebra/, so we pass O=~/zebra to make.  Dependening on where
      we run the build from, we see:
      
      	make run in dir		$(OUTPUT) dir
      	=======================	==================
      	linux			~/zebra/tools/perf/
      	linux/tools		~/zebra/perf/
      	linux/tools/perf	~/zebra/
      
      and if O= is not set, we get:
      
      	make run in dir		$(OUTPUT) dir
      	=======================	==================
      	linux			linux/tools/perf/
      	linux/tools		linux/tools/perf/
      	linux/tools/perf	linux/tools/perf/
      
      The output directories are created by the descend function if they don't
      already exist.
      Signed-off-by: NDavid Howells <dhowells@redhat.com>
      Cc: Borislav Petkov <bp@amd64.org>
      Cc: Ingo Molnar <mingo@kernel.org>
      Cc: Linus Torvalds <torvalds@linux-foundation.org>
      Cc: Namhyung Kim <namhyung@gmail.com>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Link: http://lkml.kernel.org/r/1378.1352379110@warthog.procyon.org.ukSigned-off-by: NArnaldo Carvalho de Melo <acme@redhat.com>
      9db48cd5
  20. 11 11月, 2012 1 次提交
  21. 05 11月, 2012 1 次提交
  22. 29 10月, 2012 1 次提交
  23. 21 10月, 2012 1 次提交
  24. 20 10月, 2012 1 次提交
  25. 19 10月, 2012 1 次提交
  26. 17 10月, 2012 1 次提交
  27. 15 10月, 2012 1 次提交
  28. 10 10月, 2012 2 次提交
  29. 03 10月, 2012 3 次提交
  30. 01 10月, 2012 1 次提交
  31. 24 9月, 2012 1 次提交
  32. 17 9月, 2012 1 次提交
  33. 09 9月, 2012 1 次提交
  34. 02 9月, 2012 1 次提交
  35. 31 8月, 2012 1 次提交
  36. 23 8月, 2012 1 次提交