10 Sep, 2018

1 commit

  • This is a respin with a wider audience (all that get_maintainer returned)
    and I know this spams a *lot* of people. Not sure what would be the correct
    way, so my apologies for ruining your inbox.

    The 00-INDEX files are supposed to give a summary of all files present
    in a directory, but these files are horribly out of date and their
    usefulness is brought into question. Often a simple "ls" would reveal
    the same information as the filenames are generally quite descriptive as
    a short introduction to what the file covers (it should not surprise
    anyone what Documentation/sched/sched-design-CFS.txt covers)

    A few years back it was mentioned that these files were no longer really
    needed, and they have since then grown further out of date, so perhaps
    it is time to just throw them out.

    A short status yields the following _outdated_ 00-INDEX files, first
    counter is files listed in 00-INDEX but missing in the directory, last
    is files present but not listed in 00-INDEX.

    List of outdated 00-INDEX:
    Documentation: (4/10)
    Documentation/sysctl: (0/1)
    Documentation/timers: (1/0)
    Documentation/blockdev: (3/1)
    Documentation/w1/slaves: (0/1)
    Documentation/locking: (0/1)
    Documentation/devicetree: (0/5)
    Documentation/power: (1/1)
    Documentation/powerpc: (0/5)
    Documentation/arm: (1/0)
    Documentation/x86: (0/9)
    Documentation/x86/x86_64: (1/1)
    Documentation/scsi: (4/4)
    Documentation/filesystems: (2/9)
    Documentation/filesystems/nfs: (0/2)
    Documentation/cgroup-v1: (0/2)
    Documentation/kbuild: (0/4)
    Documentation/spi: (1/0)
    Documentation/virtual/kvm: (1/0)
    Documentation/scheduler: (0/2)
    Documentation/fb: (0/1)
    Documentation/block: (0/1)
    Documentation/networking: (6/37)
    Documentation/vm: (1/3)

    Then there are 364 subdirectories in Documentation/ with several files that
    are missing 00-INDEX alltogether (and another 120 with a single file and no
    00-INDEX).

    I don't really have an opinion to whether or not we /should/ have 00-INDEX,
    but the above 00-INDEX should either be removed or be kept up to date. If
    we should keep the files, I can try to keep them updated, but I rather not
    if we just want to delete them anyway.

    As a starting point, remove all index-files and references to 00-INDEX and
    see where the discussion is going.

    Signed-off-by: Henrik Austad
    Acked-by: "Paul E. McKenney"
    Just-do-it-by: Steven Rostedt
    Reviewed-by: Jens Axboe
    Acked-by: Paul Moore
    Acked-by: Greg Kroah-Hartman
    Acked-by: Mark Brown
    Acked-by: Mike Rapoport
    Cc: [Almost everybody else]
    Signed-off-by: Jonathan Corbet

    Henrik Austad
     

21 Mar, 2018

2 commits


24 Oct, 2016

3 commits


15 Aug, 2016

1 commit

  • Support for i386 was removed in v3.8, delete the paragraph that says
    processor types above 386 won't work on that architecture. It's obsolete
    information and potentially confusing. Also change a couple of
    "arch/i386/" paths to one that exists now, using "arch/x86/" instead.

    Signed-off-by: Øyvind A. Holm
    Signed-off-by: Jonathan Corbet

    Øyvind A. Holm
     

16 Apr, 2016

1 commit


26 Jan, 2016

1 commit


19 Sep, 2015

1 commit


11 Jul, 2015

1 commit


20 Mar, 2015

2 commits


29 Oct, 2012

1 commit


26 Oct, 2012

1 commit


08 Oct, 2012

1 commit

  • Someone (over a year ago :-p) asked me to document localmodconfig in the
    README file in the source code. I thought it was a good idea but other
    things were more important and I simply forgot about it. Well, I
    stumbled on the email asking me about this and I'm sending it out now.

    Signed-off-by: Steven "Mr. Procrastinator" Rostedt
    Signed-off-by: Linus Torvalds

    Steven Rostedt
     

17 Apr, 2012

8 commits


02 Jul, 2011

1 commit


24 Feb, 2011

1 commit


13 Oct, 2010

1 commit


15 Jun, 2009

1 commit


10 Jun, 2009

1 commit


21 Feb, 2009

1 commit

  • It should be Documentation/build/kconfig.txt.

    Introduced by commit 2af238e455ef5fd31c2f7a06c2db3f13d843b9bf
    ("kbuild: make *config usage docs").

    Signed-off-by: Li Zefan
    Cc: Sam Ravnborg
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Li Zefan
     

03 Jan, 2009

1 commit

  • Create a kconfig user assistance guide, with a few tips and hints
    about using menuconfig, xconfig, and gconfig.

    Mostly contains user interface, environment variables, and search topics,
    along with mini.config/custom.config usage.

    Signed-off-by: Randy Dunlap
    Signed-off-by: Sam Ravnborg

    Randy Dunlap
     

18 Nov, 2007

1 commit

  • Simplify "make ARCH=x86" and fix kconfig so we again can set 64BIT in
    all.config.

    For a fix the diffstat is nice:
    6 files changed, 3 insertions(+), 36 deletions(-)

    The patch reverts these commits:
    - 0f855aa64b3f63d35a891510cf7db932a435c116 ("kconfig: add helper to set
    config symbol from environment variable")
    - 2a113281f5cd2febbab21a93c8943f8d3eece4d3 ("kconfig: use $K64BIT to
    set 64BIT with all*config targets")

    Roman Zippel pointed out that kconfig supported string compares so
    the additional complexity introduced by the above two patches were
    not needed.

    With this patch we have following behaviour:

    # make {allno,allyes,allmod,rand}config [ARCH=...]
    option \ host arch | 32bit | 64bit
    =====================================================
    ./. | 32bit | 64bit
    ARCH=x86 | 32bit | 32bit
    ARCH=i386 | 32bit | 32bit
    ARCH=x86_64 | 64bit | 64bit

    The general rule are that ARCH= and native architecture takes
    precedence over the configuration.

    So make ARCH=i386 [whatever] will always build a 32-bit kernel
    no matter what the configuration says. The configuration will
    be updated to 32-bit if it was configured to 64-bit and the
    other way around.

    This behaviour is consistent with previous behaviour so no
    suprises here.

    make ARCH=x86 will per default result in a 32-bit kernel but as
    the only ARCH= value x86 allow the user to select between 32-bit
    and 64-bit using menuconfig.

    Signed-off-by: Sam Ravnborg
    Cc: Roman Zippel
    Cc: Andreas Herrmann
    Cc: Thomas Gleixner
    Cc: Ingo Molnar
    Cc: "H. Peter Anvin"
    Signed-off-by: Linus Torvalds

    Sam Ravnborg
     

13 Nov, 2007

1 commit

  • The variable K64BIT can now be used to select the
    value of CONFIG_64BIT.

    This is for example useful for powerpc to generate
    allmodconfig for both bit sizes - like this:
    make ARCH=powerpc K64BIT=y
    make ARCH=powerpc K64BIT=n

    To use this the Kconfig file must use "64BIT" as the
    config value to select between 32 and 64 bit.

    Signed-off-by: Sam Ravnborg
    Cc: Roman Zippel

    Sam Ravnborg
     

18 Feb, 2007

1 commit

  • Mikael Pettersson pointed out to me that a recent patch of mine (commit
    620034c84d1d939717bdfbe02c51a3fee43541c3), that made some corrections to the
    README file, accidentally listed the Cris architecture twice. Whoops.

    This patch removes the duplicate.

    Signed-off-by: Jesper Juhl
    Signed-off-by: Adrian Bunk

    Jesper Juhl
     

24 Jan, 2007

1 commit


07 Dec, 2006

1 commit

  • Here's a small patch which

    - adds a few archs to the current list of supported platforms.
    - adds a few missing slashes at the end of URLs.
    - adds a few references to additional documentation.
    - adds "make config" to the list of possible configuration targets.
    - makes a few other minor changes.

    Signed-off-by: Jesper Juhl
    [ Ben Nizette points out AVR32 arch too ]
    Signed-off-by: Linus Torvalds

    Jesper Juhl
     

20 Apr, 2006

1 commit

  • Replace outdated help message with a reference to README. Update README
    for make *config variants and environment variable info.

    Signed-off-by: Randy Dunlap
    Acked-by: Sam Ravnborg
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Randy Dunlap
     

21 Mar, 2006

1 commit


17 Jan, 2006

1 commit


09 Jan, 2006

1 commit

  • Remove various things which were checking for gcc-1.x and gcc-2.x compilers.

    From: Adrian Bunk

    Some documentation updates and removes some code paths for gcc < 3.2.

    Acked-by: Russell King
    Signed-off-by: Adrian Bunk
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Andrew Morton