1. 09 Jun, 2014 1 commit
  2. 13 Sep, 2013 1 commit
  3. 15 Aug, 2013 1 commit
  4. 18 Jun, 2013 1 commit
  5. 20 May, 2013 1 commit
  6. 14 Dec, 2012 1 commit
  7. 26 Jul, 2012 1 commit
  8. 28 Jun, 2012 3 commits
    • Yann E. MORIN's avatar
      scripts/config: add option to undef a symbol · d5bfb6b3
      Yann E. MORIN authored
      It is currently possible to enable, disable or modularise
      a symbol. Also, an undefined symbol is reported as such.
      
      Add a new command to undefine a symbol, by removing the
      corresponding line from the .config file.
      Signed-off-by: 's avatar"Yann E. MORIN" <yann.morin.1998@free.fr>
      Signed-off-by: 's avatarMichal Marek <mmarek@suse.cz>
      d5bfb6b3
    • Yann E. MORIN's avatar
      scripts/config: allow alternate prefix to config option symbol · f5ef2f7b
      Yann E. MORIN authored
      While the Linux kernel uses 'CONFIG_' as a prefix to the config options
      symbols, many projects that use kconfig may use different prefixes, or
      even none at all.
      
      If the CONFIG_ environment variable is set, use it as the prefix (empty
      is a valid prefix). Otherwise, use the default prefix 'CONFIG_'.
      
      This matches the support for alternate prefixes in scripts/kconfig/lkc.h,
      which uses the same logic (albeit with a C define instead of an environment
      variable).
      Signed-off-by: 's avatar"Yann E. MORIN" <yann.morin.1998@free.fr>
      Signed-off-by: 's avatarMichal Marek <mmarek@suse.cz>
      f5ef2f7b
    • Yann E. MORIN's avatar
      scripts/config: add option to not upper-case symbols · 4edc7e32
      Yann E. MORIN authored
      Currently, scripts/config mangles the config option symbols to always
      be upper-case.
      
      While the Linux kernel almost exclusively uses upper-case symbols, there
      are still a few symbols with lower-case which this script can not handle:
      
        $ grep -r -E '^[[:space:]]*config[[:space:]]+[^[:space:]]*[[:lower:]][^[:space:]=.]*$' . |wc -l
        173
      (that's roughly 1.3% of the symbols in 3.5-rc1)
      
      Eg.:
        ./arch/arm/Kconfig:config VFPv3
        ./arch/powerpc/platforms/Kconfig.cputype:config 40x
        ./arch/x86/Kconfig:config SCx200HR_TIMER
        ./drivers/video/console/Kconfig:config FONT_8x8
        ./drivers/video/Kconfig:config NTSC_640x480
      
      Also, other projects that use kconfig may allow for lower- or mixed-case
      symbols, and may find easier to reuse this script than implement each
      their own (potentially flawed) logic. For such a use-case, see:
          http://marc.info/?l=linux-kbuild&m=133409932115848&w=2
      
      This patch adds a new option to keep the given case, and keep the current
      default to upper-case the symbols.
      Signed-off-by: 's avatar"Yann E. MORIN" <yann.morin.1998@free.fr>
      Signed-off-by: 's avatarMichal Marek <mmarek@suse.cz>
      4edc7e32
  9. 15 May, 2012 1 commit
    • Yann E. MORIN's avatar
      scripts/config: properly report and set string options · d6686da8
      Yann E. MORIN authored
      Currently, scripts/config removes the leading double-quote from
      string options, but leaves the trailing double-quote.
      
      Also, double-quotes in a string are escaped, but scripts/config
      does not unescape those when printing
      
      Finally, scripts/config does not escape double-quotes when setting
      string options.
      
      Eg. the current behavior:
          $ grep -E '^CONFIG_FOO=' .config
          CONFIG_FOO="Bar \"Buz\" Meh"
          $ ./scripts/config -s FOO
          Bar \"Buz\" Meh"
          $ ./scripts/config --set-str FOO 'Alpha "Bravo" Charlie'
          $ grep -E '^CONFIG_FOO=' .config
          CONFIG_FOO="Alpha "Bravo" Charlie"
      
      Fix those three, giving this new behavior:
          $ grep -E '^CONFIG_FOO=' .config
          CONFIG_FOO="Bar \"Buz\" Meh"
          $ ./scripts/config -s FOO
          Bar "Buz" Meh
          $ ./scripts/config --set-str FOO 'Alpha "Bravo" Charlie'
          $ grep -E '^CONFIG_FOO=' .config
          CONFIG_FOO="Alpha \"Bravo\" Charlie"
      Signed-off-by: 's avatar"Yann E. MORIN" <yann.morin.1998@free.fr>
      Acked-by: 's avatarAndi Kleen <andi@firstfloor.org>
      Signed-off-by: 's avatarMichal Marek <mmarek@suse.cz>
      d6686da8
  10. 15 Dec, 2010 1 commit
  11. 25 Nov, 2010 1 commit
  12. 14 Jun, 2009 3 commits
  13. 14 Jan, 2009 1 commit
  14. 07 Jan, 2009 1 commit
    • Andi Kleen's avatar
      kconfig: add script to manipulate .config files on the command line · 8e54701e
      Andi Kleen authored
      I often change single options in .config files. Instead of using
      an editor or one of the frontends it's convenient to do this from
      the command line. It's also useful to do from automated build scripts
      when building different variants from a base config file.
      
      I extracted most of the CONFIG manipulation code from one of my
      build scripts into a new shell script scripts/config
      
      The script is not integrated with the normal Kconfig machinery
      and doesn't do any checking against Kconfig files, but just manipulates
      that text format. This is always done at make time anyways.
      
      I believe this script would be a useful standard addition for scripts/*
      
      Sample usage:
      
      ./scripts/config --disable smp
      Disable SMP in .config file
      
      ./scripts/config --file otherdir/.config --module e1000e
      Enable E1000E as module in otherdir/.config
      
      ./scripts/config --state smp
      y
      Check state of config option CONFIG_SMP
      
      After merging into git please make scripts/config executable
      Signed-off-by: 's avatarAndi Kleen <ak@linux.intel.com>
      Signed-off-by: 's avatarSam Ravnborg <sam@ravnborg.org>
      8e54701e