19 Jul, 2010

1 commit

• a2531293d   update email address ... Browse Code »

  pavel@suse.cz no longer works, replace it with working address.

  Signed-off-by: Pavel Machek
  Signed-off-by: Jiri Kosina

  Pavel Machek

  2010-07-19 16:56:54 +0800  

28 Apr, 2010

1 commit

• 05be7a868   doc: Change urls for sparse ... Browse Code »

  The location of the sparse web page and git tree were no longer
  valid. This changes them to point to the current versions.

  Signed-off-by: Bill Pemberton
  Signed-off-by: Jiri Kosina

  Bill Pemberton

  2010-04-28 04:59:07 +0800  

11 Apr, 2009

1 commit

• 20375bf82   Documentation: explain the difference between __bitwise and __bitwise__ ... Browse Code »

  Simply added explanation from Al Viro in the following mail:
  http://lkml.indiana.edu/hypermail/linux/kernel/0802.2/3164.html

  Cc: Al Viro
  Cc: Randy Dunlap
  Signed-off-by: Sam Ravnborg

  Sam Ravnborg

  2009-04-11 14:18:11 +0800  

26 Jul, 2008

1 commit

• a887a07d5   kbuild: sparse needs CF not CHECKFLAGS ... Browse Code »

  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

  2008-07-26 04:12:39 +0800  

09 Mar, 2007

1 commit

• a55028ff7   [PATCH] update 'getting sparse' info. ... Browse Code »

  - point to the sparse webpage
  - use git:// instead of rsync://

  Signed-off-by: Dave Jones
  Signed-off-by: Linus Torvalds

  Dave Jones

  2007-03-09 08:47:58 +0800  

25 Sep, 2006

1 commit

• 1c7bafe72   kbuild: clarify "make C=" build option ... Browse Code »

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

  Signed-off-by: Sam Ravnborg

  Robert P. J. Day

  2006-09-25 16:10:56 +0800  

23 Jun, 2006

1 commit

• e83319510   [PATCH] docs: update sparse.txt with CHECK_ENDIAN ... Browse Code »

  Update the sparse documentation to omit the -Wbitwise flag example (as it
  is now passed by default), and document the kernel defines to enable
  endianness checking.

  Signed-off-by: Bob Copeland
  Signed-off-by: Andrew Morton
  Signed-off-by: Linus Torvalds

  Bob Copeland

  2006-06-23 22:43:09 +0800  

07 Nov, 2005

1 commit

• 55032eacd   [PATCH] Documentation/sparse.txt: mention CF=-Wbitwise ... Browse Code »

  Signed-off-by: Alexey Dobriyan
  Signed-off-by: Andrew Morton
  Signed-off-by: Linus Torvalds

  Alexey Dobriyan

  2005-11-07 23:53:54 +0800  

24 Sep, 2005

1 commit

• 86513e726   [PATCH] documentation: sparse no longer uses bk, but git ... Browse Code »

  Signed-off-by: Harald Welte
  Signed-off-by: Andrew Morton
  Signed-off-by: Linus Torvalds

  Harald Welte

  2005-09-24 04:35:37 +0800  

10 Sep, 2005

1 commit

• e272d5068   [PATCH] Documentation/sparse snapshot URL ... Browse Code »

  The URL for Documentation/sparse is wrong now that it is in git.

  Signed-off-by: Ben Dooks
  Signed-off-by: Andrew Morton
  Signed-off-by: Linus Torvalds

  Ben Dooks

  2005-09-10 05:03:44 +0800  

17 Apr, 2005

1 commit

• 1da177e4c   Linux-2.6.12-rc2 ... Browse Code »

  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

  2005-04-17 06:20:36 +0800