1. 14 4月, 2010 1 次提交
  2. 02 2月, 2010 1 次提交
  3. 20 9月, 2009 3 次提交
  4. 29 4月, 2008 1 次提交
    • R
      kconfig: add named choice group · 5a1aa8a1
      Roman Zippel 提交于
      As choice dependency are now fully checked, it's quite easy to add support
      for named choices. This lifts the restriction that a choice value can only
      appear once, although it still has to be within the same group,
      but multiple choices can be joined by giving them a name.
      While at it I cleaned up a little the choice type logic to simplify it a
      bit.
      Signed-off-by: NRoman Zippel <zippel@linux-m68k.org>
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      5a1aa8a1
  5. 03 2月, 2008 1 次提交
    • S
      kconfig: ignore select of unknown symbol · 603d4988
      Sam Ravnborg 提交于
      We have had warnings for a long time about select of unknow symbol
      but the warnings does not really makes sense since we may
      select a symbol that is relevant and defined in one
      arch but not in another arch.
      And as long as we do not use a common set of Kconfig files
      for all archs lets just ignore this case.
      
      Previously we have used this to find bad uses of
      select but we need a more relaible method to do so.
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      Cc: Roman Zippel <zippel@linux-m68k.org>
      603d4988
  6. 29 1月, 2008 4 次提交
  7. 20 10月, 2007 1 次提交
    • L
      Revert "kconfig: tristate choices with mixed tristate and boolean values" · e8b8c977
      Linus Torvalds 提交于
      This reverts commit a5bf3d89.
      
      David Brownell notes that this causes a regression visible in the
      drivers/usb/gadget Kconfig file:
      
        "That Kconfig hasn't changed (other than adding new drivers), and it's
         worked that way for several years now ...  so the issue seems to be
         changes in menuconfig/kconfig/etc semantics.
      
         The issue is that when USB_GADGET=m, it's no longer possible to
         configure peripheral controller drivers as modules ...  the
         controller drivers can now only be configured for static linkage.
      
         It should be making a choice of one of the controller drivers which
         could work on the target system, and allow that driver to be linked
         either as a module (ok iff USB_GADGET=m) or statically."
      
      Reverting this commit resolves the problem, and also fixes a second
      problem that David noticed: various dependent options couldn't be enabled.
      Tested-and-reported-by: NDavid Brownell <david-b@pacbell.net>
      Cc: Randy Dunlap <rdunlap@xenotime.net>
      Cc: Jan Beulich <jbeulich@novell.com>,
      Cc: Andrew Morton <akpm@linux-foundation.org>,
      Cc: Sam Ravnborg <sam@ravnborg.org>,
      Cc: Roman Zippel <zippel@linux-m68k.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      e8b8c977
  8. 13 10月, 2007 1 次提交
  9. 26 7月, 2007 1 次提交
    • S
      kconfig: attach help text to menus · 03d29122
      Sam Ravnborg 提交于
      Roman Zippel wrote:
      > A simple example would be
      > help texts, right now they are per symbol, but they should really be per
      > menu, so archs can provide different help texts for something.
      
      This patch does this and at the same time introduce a few API
      funtions used to access the help text.
      
      The relevant api functions are introduced in the various frontends.
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      Cc: Roman Zippel <zippel@linux-m68k.org>
      03d29122
  10. 03 5月, 2007 1 次提交
  11. 09 6月, 2006 3 次提交
  12. 09 11月, 2005 2 次提交
  13. 29 7月, 2005 1 次提交
  14. 06 5月, 2005 1 次提交
    • A
      [PATCH] Kconfig i18n support · 3b9fa093
      Arnaldo Carvalho de Melo 提交于
      This patch adds i18n support for make *config, allowing users to have the
      config process in their own language.
      
      No printk was harmed in the process, don't worry, so all the bug reports,
      kernel messages, etc, remain in english, just the user tools to configure
      the kernel are internationalized.
      
      Users not interested in translations can just unset the related LANG,
      LC_ALL, etc env variables and have the config process in plain english,
      something like:
      
      LANG= make menuconfig
      
      is enough for having the whole config process in english. Or just don't
      install any translation file.
      
      Translations for brazilian portuguese are being done by a team of
      volunteers at:
      
      http://www.visionflex.inf.br/kernel_ptbr/pmwiki.php/Principal/Traducoes
      
      To start the translation process:
      
        make update-po-config
      
        This will generate the pot template named scripts/kconfig/linux.pot,
        copy it to, say, ~/es.po, to start the translation for spanish.
      
      To test your translation, as root issue this command:
      
        msgfmt -o /usr/share/locale/es/LC_MESSAGES/linux.mo ~/es.po
      
        Replace "es" with your language code.
      
        Then execute, for instance:
      
        make menuconfig
      
      The current patch doesn't use any optimization to reduce the size of the
      generated .mo file, it is possible to use the config option as a key, but
      this doesn't prevent the current patch from being used or the translations
      done under the current scheme to be in any way lost if we chose to do any
      kind of keying.
      
      Thanks to Fabricio Vaccari for starting the pt_BR (brazilian portuguese)
      translation effort, Thiago Maciera for helping me with the gconf.cc (QT
      frontent) i18n coding and to all the volunteers that are already working on
      the first translation, to pt_BR.
      
      I left the question on whether to ship the translations with the stock kernel
      sources to be discussed here, please share your suggestions.
      Signed-off-by: NArnaldo Carvalho de Melo <acme@conectiva.com.br>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: Linus Torvalds <torvalds@osdl.org
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      3b9fa093
  15. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4