1. 24 3月, 2012 4 次提交
  2. 08 2月, 2012 1 次提交
    • J
      checkpatch: Warn on code with 6+ tab indentation · 8eef05dd
      Joe Perches 提交于
      Overly indented code should be refactored.
      
      Suggest refactoring excessive indentation of of
      if/else/for/do/while/switch statements.
      
      For example:
      
      $ cat t.c
      #include <stdio.h>
      #include <stdlib.h>
      
      int main(int argc, char **argv)
      {
      
      	if (1)
      		if (2)
      			if (3)
      				if (4)
      					if (5)
      						if (6)
      							if (7)
      								if (8)
      									;
      	return 0;
      }
      
      $ ./scripts/checkpatch.pl -f t.c
      WARNING: Too many leading tabs - consider code refactoring
      #12: FILE: t.c:12:
      +						if (6)
      
      WARNING: Too many leading tabs - consider code refactoring
      #13: FILE: t.c:13:
      +							if (7)
      
      WARNING: Too many leading tabs - consider code refactoring
      #14: FILE: t.c:14:
      +								if (8)
      
      total: 0 errors, 3 warnings, 17 lines checked
      
      t.c has style problems, please review.
      
      If any of these errors are false positives, please report
      them to the maintainer, see CHECKPATCH in MAINTAINERS.
      Signed-off-by: NJoe Perches <joe@perches.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      8eef05dd
  3. 11 1月, 2012 15 次提交
  4. 01 11月, 2011 2 次提交
  5. 15 9月, 2011 1 次提交
  6. 31 8月, 2011 1 次提交
    • A
      script/checkpatch.pl: warn about deprecated use of EXTRA_{A,C,CPP,LD}FLAGS · c68e5878
      Arnaud Lacombe 提交于
      Usage of these flags has been deprecated for nearly 4 years by:
      
          commit f77bf014
          Author: Sam Ravnborg <sam@neptun.(none)>
          Date:   Mon Oct 15 22:25:06 2007 +0200
      
              kbuild: introduce ccflags-y, asflags-y and ldflags-y
      
      Moreover, these flags (at least EXTRA_CFLAGS) have been documented for command
      line use. By default, gmake(1) do not override command line setting, so this is
      likely to result in build failure or unexpected behavior.
      
      Warn about their introduction in Makefile or Kbuild files.
      
      Cc: Sam Ravnborg <sam@ravnborg.org>
      Cc: Andy Whitcroft <apw@canonical.com>
      Signed-off-by: NArnaud Lacombe <lacombar@gmail.com>
      Signed-off-by: NMichal Marek <mmarek@suse.cz>
      c68e5878
  7. 26 8月, 2011 1 次提交
  8. 26 7月, 2011 7 次提交
  9. 16 6月, 2011 1 次提交
  10. 25 5月, 2011 3 次提交
  11. 31 3月, 2011 1 次提交
  12. 23 3月, 2011 3 次提交
    • D
      checkpatch: warn about memset with swapped arguments · 309c00c7
      Dave Jones 提交于
      Because the second and third arguments of memset have the same type, it
      turns out to be really easy to mix them up.
      
      This bug comes up time after time, so checkpatch should really be checking
      for it at patch submission time.
      Signed-off-by: NDave Jones <davej@redhat.com>
      Cc: Steven Rostedt <rostedt@goodmis.org>
      Cc: Andy Whitcroft <apw@shadowen.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      309c00c7
    • M
      scripts/checkpatch.pl: reset rpt_cleaners warnings · b0781216
      Mike Frysinger 提交于
      If you run checkpatch against multiple patches, and one of them has a
      whitespace issue which can be helped via a script (rpt_cleaners), you will
      see the same NOTE over and over for all subsequent patches.  It makes it
      seem like those patches also have whitespace problems when in reality,
      there's only one or two bad apples.
      
      So reset rpt_cleaners back to 0 after we've issued the note so that it
      only shows up near the patch with the actual problems.
      Signed-off-by: NMike Frysinger <vapier@gentoo.org>
      Cc: Andy Whitcroft <apw@canonical.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      b0781216
    • A
      kstrto*: converting strings to integers done (hopefully) right · 33ee3b2e
      Alexey Dobriyan 提交于
      1. simple_strto*() do not contain overflow checks and crufty,
         libc way to indicate failure.
      2. strict_strto*() also do not have overflow checks but the name and
         comments pretend they do.
      3. Both families have only "long long" and "long" variants,
         but users want strtou8()
      4. Both "simple" and "strict" prefixes are wrong:
         Simple doesn't exactly say what's so simple, strict should not exist
         because conversion should be strict by default.
      
      The solution is to use "k" prefix and add convertors for more types.
      Enter
      	kstrtoull()
      	kstrtoll()
      	kstrtoul()
      	kstrtol()
      	kstrtouint()
      	kstrtoint()
      
      	kstrtou64()
      	kstrtos64()
      	kstrtou32()
      	kstrtos32()
      	kstrtou16()
      	kstrtos16()
      	kstrtou8()
      	kstrtos8()
      
      Include runtime testsuite (somewhat incomplete) as well.
      
      strict_strto*() become deprecated, stubbed to kstrto*() and
      eventually will be removed altogether.
      
      Use kstrto*() in code today!
      
      Note: on some archs _kstrtoul() and _kstrtol() are left in tree, even if
            they'll be unused at runtime. This is temporarily solution,
            because I don't want to hardcode list of archs where these
            functions aren't needed. Current solution with sizeof() and
            __alignof__ at least always works.
      Signed-off-by: NAlexey Dobriyan <adobriyan@gmail.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      33ee3b2e