18 Dec, 2012

1 commit

  • The context feature of sparse is used with the Linux kernel sources to
    check for imbalanced uses of locks. Document the annotations defined in
    include/linux/compiler.h that tell sparse what to expect when a lock is
    held on function entry, exit, or both.

    Signed-off-by: Ed Cashin
    Reviewed-by: Josh Triplett
    Acked-by: Christopher Li
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Ed Cashin
     

19 Jul, 2010

1 commit


28 Apr, 2010

1 commit


11 Apr, 2009

1 commit


26 Jul, 2008

1 commit

  • Documentation/sparse.txt tells to use:

    make C=2 CHECKFLAGS="-D__CHECK_ENDIAN__"

    However, this still doesn't enable endian checks. The correct syntax is:

    make C=2 CF="-D__CHECK_ENDIAN__"

    This documentation bug was introduced by the following commit:

    commit 1c7bafe7206d928eaccbcbd08d868733e0fb7054
    Author: Robert P. J. Day
    Date: Wed Sep 13 07:57:50 2006 -0400

    kbuild: clarify "make C=" build option

    Clarify the use of "make C=" in the top-level Makefile, and fix a
    typo in the Documentation file.

    Signed-off-by: Sam Ravnborg

    This `typo' was not a typo, as `CF' had been introduced much earlier, by:

    commit 7b49bb9aff8b14d15da58111d8908c877c0a525e
    Author: viro@ZenIV.linux.org.uk
    Date: Fri Sep 9 21:14:35 2005 +0100

    [PATCH] kbuild: CF= passes arguments to sparse

    Allows to add to sparse arguments without mutilating makefiles - just
    pass CF= and they will be added to CHECKFLAGS.

    Signed-off-by: Al Viro
    Signed-off-by: Sam Ravnborg

    Signed-off-by: Geert Uytterhoeven
    Signed-off-by: Sam Ravnborg

    Geert Uytterhoeven
     

09 Mar, 2007

1 commit


25 Sep, 2006

1 commit


23 Jun, 2006

1 commit


07 Nov, 2005

1 commit


24 Sep, 2005

1 commit


10 Sep, 2005

1 commit


17 Apr, 2005

1 commit

  • 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!

    Linus Torvalds