17 Jul, 2007

1 commit

  • This version brings a number of new checks, fixes for flase
    positives, plus a clarification of the output to better guide use. Of
    note:

    - checks for documentation for new __setup calls
    - clearer reporting where braces and parenthesis are involved
    - reports for closing brace and semi-colon spacing
    - reports on unwanted externs

    This patch includes an update to the documentation on checkpatch.pl
    itself to clarify when it should be used and to indicate that it
    is not intended as the final arbitor of style.

    Full changelog:

    Andy Whitcroft (19):
    Version: 0.07
    ensure we do not apply control brace checks to preprocesor directives
    add {u,s}{8,16,32,64} to the type matcher
    accept lack of spacing after the semicolons in for (;;)
    report new externs in .c files
    fix up typedef exclusion for function prototypes
    else trailing statements check need to account for \ at end of line
    add enums to the type matcher
    add missing check descriptions
    suppress double reporting of ** spacing
    report on do{ spacing issues
    include an example of the brace/parenthesis in output
    check for spacing after closing braces
    prevent double reports on pointer spacing issues
    handle blank continuation lines on macros
    classify all reports error, warning, or check
    revamp hanging { checks and apply in context
    no spaces after the last ; in a for is ok
    check __setup has a corresponding addition to documentation

    David Woodhouse (1):
    limit character set used in patches and descriptions to UTF-8

    Signed-off-by: Andy Whitcroft
    Cc: David Woodhouse
    Cc: "Randy.Dunlap"
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Andy Whitcroft
     

07 Jul, 2007

1 commit

  • A bug in headers_install for ARCH=x86_64 yields an asm/ directory full of
    files all of which are using the same #ifdef guard, "__ASM_STUB_" with no
    postfix. So the second and later asm files #included in the same C file
    (often through standard headers like ioctl.h) yields no symbols.

    Strangeness with the Ubuntu 'tell me if I support something that's not
    explcitly mentioned in POSIX, and I'll strip it out' shell, I believe.

    We don't need the 'export' but we do need a semicolon at the end of the
    FNAME line:

    Signed-off-by: David Woodhouse
    Signed-off-by: Rob Landley
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    David Woodhouse
     

29 Jun, 2007

1 commit

  • Not all the world is an i386. Many architectures need 64-bit arguments to be
    aligned in suitable pairs of registers, and the original
    sys_sync_file_range(int, loff_t, loff_t, int) was therefore wasting an
    argument register for padding after the first integer. Since we don't
    normally have more than 6 arguments for system calls, that left no room for
    the final argument on some architectures.

    Fix this by introducing sys_sync_file_range2(int, int, loff_t, loff_t) which
    all fits nicely. In fact, ARM already had that, but called it
    sys_arm_sync_file_range. Move it to fs/sync.c and rename it, then implement
    the needed compatibility routine. And stop the missing syscall check from
    bitching about the absence of sys_sync_file_range() if we've implemented
    sys_sync_file_range2() instead.

    Tested on PPC32 and with 32-bit and 64-bit userspace on PPC64.

    Signed-off-by: David Woodhouse
    Acked-by: Russell King
    Cc: Arnd Bergmann
    Cc: Paul Mackerras
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    David Woodhouse
     

24 Jun, 2007

2 commits

  • Update to checkpatch.pl v0.06. Of note:

    - do { and else handled correctly as control structures for { matching
    - trailing whitespace correctly tripped when line otherwise empty
    - support for const, including const foo * const bar
    - multiline macros defining values correctly reported

    This version of checkpatch.pl can be found at the following URL:

    http://www.kernel.org/pub/linux/kernel/people/apw/checkpatch/checkpatch.pl-0.06

    Full Changelog:

    Andy Whitcroft (14):
    Version: 0.06
    cleanup the Type regular expression declarations
    fix up block counting
    end of line counts as a space for ++ and --
    do { needs the same checks as if, for et al
    handle "const foo * const a" as a valid type
    add spacing checks following ;
    complete whitespace lines should trip trailing whitespace check
    else is also a block control structure
    badly formatted else can trip function declaration
    detect and report trailing statements after else
    types need to be terminated by a boundary
    multiline macros defining values should be surrounded by parentheses
    soften the wording of the Signed-off-by: warnings

    Signed-off-by: Andy Whitcroft
    Cc: "Randy.Dunlap"
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Andy Whitcroft
     
  • This version brings a some new tests, and a host of changes to fix
    false positives, of particular note:

    - detect 'var ++;' and 'var --;' as a bad combination
    - multistatement #defines are now checked based on statement count
    - multistatement #defines with initialisation correctly reported
    - checks the location of the inline keywords
    - EXPORT_SYMBOL for variables are now understood
    - typedefs are loosened to handle sparse etc

    This version of checkpatch.pl can be found at the following URL:

    http://www.shadowen.org/~apw/public/checkpatch/checkpatch.pl-0.05

    Full Changelog:

    Andy Whitcroft (18):
    Version: 0.05
    macro definition checks should be for a single statement
    avoid assignements only in if conditionals
    declarations of function pointers need no space
    multiline macros which are purely initialisation cannot be wrapped
    EXPORT_SYMBOL can also directly follow a variable definition
    check on the location of the inline keyword
    EXPORT_SYMBOL needs to allow for attributes
    ensure we do not find C99 // in strings
    handle malformed #include lines
    accept the {0,} form
    typedefs are sensible for defining function pointer parameters
    ensure { handling correctly handles nested switch() statements
    trailing whitespace checks are not anchored
    typedefs for sparse bitwise annotations make sense
    update the type matcher to include sparse annotations
    clean up indent and spacing

    Signed-off-by: Andy Whitcroft
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Andy Whitcroft
     

12 Jun, 2007

1 commit

  • There's a special .cranges section that is almost always generated,
    with data being moved to the appropriate section by the linker at a later
    stage.

    To give a bit of background, sh64 has both a native SHmedia instruction
    set (32-bit instructions) and SHcompact (which is compatability with
    normal SH -- 16-bit, a massively reduced register set, etc.). code ranges
    are emitted when we're using the 32-bit ABI, but not the 64-bit one.

    It is a special staging section used solely by binutils where code with
    different flags get placed (more specifically differing flags for input
    and output sections), before being lazily merged by the linker.

    The closest I've been able to find to documentation is:
    http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/ld/emultempl/sh64elf.em?rev=1.10&content-type=text/x-cvsweb-markup&cvsroot=src

    It's an array of 8-byte Elf32_CRange structure given in
    http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/bfd/elf32-sh64.h?rev=1.4&content-type=text/x-cvsweb-markup&cvsroot=src
    that describes for which ISA a range is used.

    Silence the warnings by allowing references from .init.text to .cranges.

    The following warnings are fixed:

    WARNING: init/built-in.o(.cranges+0x0): Section mismatch: reference to .init.text:
    WARNING: init/built-in.o(.cranges+0xa): Section mismatch: reference to .init.text:
    WARNING: init/built-in.o(.cranges+0x14): Section mismatch: reference to .init.text:
    WARNING: init/built-in.o(.cranges+0x1e): Section mismatch: reference to .init.text:
    WARNING: init/built-in.o(.cranges+0x28): Section mismatch: reference to .init.text:
    WARNING: init/built-in.o(.cranges+0x32): Section mismatch: reference to .init.text:
    WARNING: kernel/built-in.o(.cranges+0x50): Section mismatch: reference to .init.text:
    WARNING: kernel/built-in.o(.cranges+0x5a): Section mismatch: reference to .init.text:
    WARNING: kernel/built-in.o(.cranges+0x64): Section mismatch: reference to .init.text:
    WARNING: kernel/built-in.o(.cranges+0xfa): Section mismatch: reference to .init.text:
    WARNING: kernel/built-in.o(.cranges+0x104): Section mismatch: reference to .init.text:
    WARNING: kernel/built-in.o(.cranges+0x10e): Section mismatch: reference to .init.text:
    WARNING: kernel/built-in.o(.cranges+0x14a): Section mismatch: reference to .init.text:
    WARNING: kernel/built-in.o(.cranges+0x154): Section mismatch: reference to .init.text:
    WARNING: kernel/built-in.o(.cranges+0x15e): Section mismatch: reference to .init.text:
    WARNING: mm/built-in.o(.cranges+0x6e): Section mismatch: reference to .init.text:
    WARNING: mm/built-in.o(.cranges+0x78): Section mismatch: reference to .init.text:
    WARNING: mm/built-in.o(.cranges+0x82): Section mismatch: reference to .init.text:
    WARNING: mm/built-in.o(.cranges+0xaa): Section mismatch: reference to .init.text:
    WARNING: fs/built-in.o(.cranges+0x136): Section mismatch: reference to .init.text:
    WARNING: fs/built-in.o(.cranges+0x140): Section mismatch: reference to .init.text:
    WARNING: fs/built-in.o(.cranges+0x14a): Section mismatch: reference to .init.text:
    WARNING: fs/built-in.o(.cranges+0x168): Section mismatch: reference to .init.text:
    WARNING: fs/built-in.o(.cranges+0x1f4): Section mismatch: reference to .init.text:
    WARNING: fs/built-in.o(.cranges+0x1fe): Section mismatch: reference to .init.text:
    WARNING: net/built-in.o(.cranges+0x302): Section mismatch: reference to .init.text:
    WARNING: net/built-in.o(.cranges+0x30c): Section mismatch: reference to .init.text:
    WARNING: net/built-in.o(.cranges+0x316): Section mismatch: reference to .init.text:
    WARNING: net/built-in.o(.cranges+0x3a2): Section mismatch: reference to .init.text:
    WARNING: net/built-in.o(.cranges+0x3ac): Section mismatch: reference to .init.text:
    WARNING: net/built-in.o(.cranges+0x4ce): Section mismatch: reference to .init.text:
    WARNING: net/built-in.o(.cranges+0x4d8): Section mismatch: reference to .init.text:

    Signed-off-by: Paul Mundt
    Cc: Kaz Kojima
    Signed-off-by: Sam Ravnborg

    Sam Ravnborg
     

09 Jun, 2007

3 commits

  • This version brings a some new tests, and a host of changes to fix
    false positives, of particular note:

    - check for and report #if 0
    - extend checking of line lengths and spacing for .pl, .sh etc
    - extends the pointer type checks to multiple levels
    - updates printk handling to track newlines
    - adds a wrapped patch detector
    - drops the leading component of the filenames
    - extends switch indent handling to switch statmentes rooted in
    the context
    - adds foo * bar single pointer checks

    This version of checkpatch.pl can be found at the following URL:

    http://www.shadowen.org/~apw/public/checkpatch/checkpatch.pl-0.04

    Full Changelog:

    Andy Whitcroft (16):
    allow checking line lengths and spacing on other source files
    clean up that whitespace
    sanitise the input line standardising the content of quotes
    clean up pointer type * and space checks
    fix up the sanitiser so it maintains the line length
    apply the printk facility checks only to the first printk in a set
    switch/case indent checks may anchor in the context
    add a wrapped patch detector
    put the #ifdef in C file checks on ice
    asm volatile is acceptable
    check for and report #if 0
    drop the leading component of the filename as patches are -p1
    use the original line when reporting operator errors
    correct spelling of Joel's name
    Version: 0.04
    add support for struct foo * bar checks

    Geert Uytterhoeven (1):
    Fix checkpatch.pl name in usage template

    Randy Dunlap (1):
    checkpatch: produce fewer lines of output

    Signed-off-by: Andy Whitcroft
    Cc: Randy Dunlap
    Cc: Joel Schopp
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Andy Whitcroft
     
  • Produce one less line of output per flagged incident.

    Change this:

    use tabs not spaces
    PATCH: /home/rddunlap/arcmsr1200014.patch4:756:
    FILE: b/drivers/scsi/arcmsr/arcmsr_hba.c:1843:
    + return PCI_ERS_RESULT_NEED_RESET;$

    to this:

    use tabs not spaces
    #756: FILE: b/drivers/scsi/arcmsr/arcmsr_hba.c:1843:
    + return PCI_ERS_RESULT_NEED_RESET;$

    Cc: Andy Whitcroft
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Randy Dunlap
     
  • This version brings a host of changes to cure false positives and
    bugs detected on patches submitted to lkml and -mm. It also brings
    a number of new tests in response to reviews, of particular note:

    - catch use of volatile
    - allow deprecated functions to be listed in feature-removal-schedule.txt
    - warn about #ifdef's in c files
    - check that spinlock_t and struct mutex use is commented
    - report on architecture specific defines being used
    - report memory barriers without an associated comment

    Full changelog:

    catch use of volatile
    convert other quoted string checks to common routine
    alloc deprecated functions to be listed in feature-removal-schedule.txt
    split out the line length and indent for each line
    improve switch block handling
    handle GNU diff context lines with no leading space
    warn about #ifdef's in c files
    tidy up tests for signed-off-by using raw mode
    check that spinlock_t and struct mutex use is commented
    syntax checks for open brace placement may drop off the bottom of hunk
    report memory barriers without an associated comment
    when a sign off is present but ugly do not report it missing
    do not mistake bitfield definitions for indented labels
    report on architecture specific defines being used
    major update to the operator checks
    prevent switch/if/while etc matching foo_switch
    generify assignement in condition error message
    introduce an operator context marker
    Version: 0.03

    Signed-off-by: Andy Whitcroft
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Andy Whitcroft
     

07 Jun, 2007

1 commit


01 Jun, 2007

1 commit

  • We are seeing increasing levels of minor patch style violations in submissions
    to the mailing lists as well as making it into the tree. These detract from
    the quality of the submission and cause unnessary work for reviewers.

    As a first step package up the current state of the patch style checker and
    include it in the kernel tree. Add instructions suggesting running it on
    submissions. This adds version v0.01 of the checkpatch.pl script.

    Signed-off-by: Andy Whitcroft
    Signed-off-by: Joel Schopp
    Cc: Randy Dunlap
    Cc: Dave Jones
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Andy Whitcroft
     

22 May, 2007

4 commits

  • This should make it stop immediately after printing the _helpful_ error
    message, rather than continuing to spit out many pages more of 'CHECK
    include/linux/foo.h' before eventually coming to a halt with something
    less obvious.

    Now I get this...
    CHECK include/linux/smb_fs.h
    /shiny/git/linux-2.6/usr/include/linux/smb_fs.h requires linux/jiffies.h, which does not exist in exported headers
    make[2]: *** [/shiny/git/linux-2.6/usr/include/linux/.check.smb_fs.h] Error 1
    make[1]: *** [linux] Error 2
    make: *** [headers_check] Error 2

    Signed-off-by-if-Sam-says-so: David Woodhouse
    [ Sam had better say so! This made me waste way too much time. - Linus]
    Signed-off-by: Linus Torvalds

    David Woodhouse
     
  • This reverts commit f892b7d480eec809a5dfbd6e65742b3f3155e50e, which
    totally broke the build on x86 with CONFIG_RELOCATABLE (which, as far as
    I can tell, is the only case where it should even matter!) due to a
    SIGSEGV in modpost.

    Cc: Sam Ravnborg
    Cc: Atsushi Nemoto
    Signed-off-by: Linus Torvalds

    Linus Torvalds
     
  • * git://git.kernel.org/pub/scm/linux/kernel/git/sam/kbuild-fix:
    mm/slab: fix section mismatch warning
    mm: fix section mismatch warnings
    init/main: use __init_refok to fix section mismatch
    kbuild: introduce __init_refok/__initdata_refok to supress section mismatch warnings
    all-archs: consolidate .data section definition in asm-generic
    all-archs: consolidate .text section definition in asm-generic
    kbuild: add "Section mismatch" warning whitelist for powerpc
    kbuild: make better section mismatch reports on i386, arm and mips
    kbuild: make modpost section warnings clearer
    kconfig: search harder for curses library in check-lxdialog.sh
    kbuild: include limits.h in sumversion.c for PATH_MAX
    powerpc: Fix the MODALIAS generation in modpost for of devices

    Linus Torvalds
     
  • Signed-off-by: Andi Kleen
    Signed-off-by: Linus Torvalds

    Andi Kleen
     

19 May, 2007

9 commits

  • modpost had two cases hardcoded for mm/
    Shift over to __init_refok and kill the
    hardcoded function names in modpost.

    This has the drawback that the functions
    will always be kept no matter configuration.
    With previous code the function were placed in
    init section if configuration allowed it.

    Signed-off-by: Sam Ravnborg

    Sam Ravnborg
     
  • Kill a special case in modpost by introducing the
    __init_refok marker.

    Signed-off-by: Sam Ravnborg

    Sam Ravnborg
     
  • Throughout the kernel there are a few legitimite references
    to init or exit sections. Most of these are covered by the
    patterns included in modpost but a few nees special attention.
    To avoid hardcoding a lot of function names in modpost introduce
    a marker so relevant function/data can be marked.
    When modpost see a reference to a init/exit function from
    a function/data marked no warning will be issued.

    Idea from: Andrew Morton

    Signed-off-by: Sam Ravnborg
    Cc: Andrew Morton

    Sam Ravnborg
     
  • This patch fixes the following class of "Section mismatch" warnings when
    building powerpc platforms.

    WARNING: arch/powerpc/kernel/built-in.o - Section mismatch: reference to .init.data:.got2 from prom_entry (offset 0x0)
    WARNING: arch/powerpc/platforms/built-in.o - Section mismatch: reference to .init.text:mpc8313_rdb_probe from .machine.desc after 'mach_mpc8313_rdb' (at offset 0x4)
    ....

    Signed-off-by: Li Yang
    Signed-off-by: Sam Ravnborg

    Li Yang
     
  • On i386, ARM and MIPS, warn_sec_mismatch() sometimes fails to show
    usefull symbol name. This is because empty 'refsym' due to 0 r_addend
    value. This patch is to adjust r_addend value, consulting with
    apply_relocate() routine in kernel code.

    Without this patch:
    MODPOST vmlinux
    WARNING: init/built-in.o - Section mismatch: reference to .init.text: from .text between 'rest_init' (at offset 0xf4) and 'try_name'
    WARNING: mm/built-in.o - Section mismatch: reference to .init.text: from .text between 'kmem_cache_create' (at offset 0x18a39) and 'cache_reap'
    WARNING: mm/built-in.o - Section mismatch: reference to .init.text: from .text between 'kmem_cache_create' (at offset 0x18a6b) and 'cache_reap'

    With this patch:
    MODPOST vmlinux
    WARNING: mm/built-in.o - Section mismatch: reference to .init.text:set_up_list3s from .text between 'kmem_cache_create' (at offset 0x18a39) and 'cache_reap'
    WARNING: mm/built-in.o - Section mismatch: reference to .init.text:set_up_list3s from .text between 'kmem_cache_create' (at offset 0x18a6b) and 'cache_reap'

    Now modpost can detect "kernel_init" name (and whitelist it) and show
    "set_up_list3s" name.

    Signed-off-by: Atsushi Nemoto
    Signed-off-by: Sam Ravnborg

    Atsushi Nemoto
     
  • Change modpost section mismatch warnings to be less confusing;
    model them on the binutils linker warnings which we all know how
    to interpret.

    Also, fix the wrong ordering of arguments for the final case -
    fromsec and refsymname were reversed.

    Signed-off-by: Russell King
    Acked-by: Acked-by: David S. Miller
    Signed-off-by: Sam Ravnborg

    Russell King
     
  • The check-lxdialog.sh script searches for "libFOO.so" which fails on OS X, due
    to their special naming of libraries like "libfoo.dylib". This patch turns
    the curses lib search into extensible loops and adds dylib as a valid
    extension.

    Signed-off-by: Mike Frysinger
    Signed-off-by: Sam Ravnborg

    Mike Frysinger
     
  • POSIX says limits.h defines PATH_MAX so we should include it (which fixes
    compiling on some systems like OS X).

    Signed-off-by: Mike Frysinger
    Signed-off-by: Sam Ravnborg

    Mike Frysinger
     
  • Since the devices may have multiple (or none) compatible properties,
    the uevent generated internally by the kernel may have multiple
    "C..." entries. So the MODALIAS stored in the module must have
    wilcard before and after the compatible entry.
    Also, if the 'compatible' field is not used for matching, there
    will be no 'C' and that must handled as well.

    The previous code handled all those case incorrectly and it
    "mostly" worked ... but not always.

    Signed-off-by: Sylvain Munaut
    Signed-off-by: Paul Mackerras
    Signed-off-by: Sam Ravnborg

    Sylvain Munaut
     

10 May, 2007

3 commits

  • * git://git.kernel.org/pub/scm/linux/kernel/git/bunk/trivial: (25 commits)
    sound: convert "sound" subdirectory to UTF-8
    MAINTAINERS: Add cxacru website/mailing list
    include files: convert "include" subdirectory to UTF-8
    general: convert "kernel" subdirectory to UTF-8
    documentation: convert the Documentation directory to UTF-8
    Convert the toplevel files CREDITS and MAINTAINERS to UTF-8.
    remove broken URLs from net drivers' output
    Magic number prefix consistency change to Documentation/magic-number.txt
    trivial: s/i_sem /i_mutex/
    fix file specification in comments
    drivers/base/platform.c: fix small typo in doc
    misc doc and kconfig typos
    Remove obsolete fat_cvf help text
    Fix occurrences of "the the "
    Fix minor typoes in kernel/module.c
    Kconfig: Remove reference to external mqueue library
    Kconfig: A couple of grammatical fixes in arch/i386/Kconfig
    Correct comments in genrtc.c to refer to correct /proc file.
    Fix more "deprecated" spellos.
    Fix "deprecated" typoes.
    ...

    Fix trivial comment conflict in kernel/relay.c.

    Linus Torvalds
     
  • This will later allow an arch to add module specific information via linker
    generated tables instead of poking directly in the module object structure.

    Signed-off-by: Roman Zippel
    Signed-off-by: Geert Uytterhoeven
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Roman Zippel
     
  • Get the kernel version string only once from the environment, thus slightly
    speeding up kernel-doc.

    Signed-off-by: Borislav Petkov
    Signed-off-by: Randy Dunlap
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Borislav Petkov
     

09 May, 2007

6 commits

  • Signed-off-by: Michael Opdenacker
    Signed-off-by: Adrian Bunk

    Michael Opdenacker
     
  • This patch shuts warnings of the sort:

    make -C /mnt/samsung_200/sam/kernel/trees/21-rc6/build \
    KBUILD_SRC=/mnt/samsung_200/sam/kernel/trees/21-rc6 \
    KBUILD_EXTMOD="" -f /mnt/samsung_200/sam/kernel/trees/21-rc6/Makefile mandocs
    make -f /mnt/samsung_200/sam/kernel/trees/21-rc6/scripts/Makefile.build obj=scripts/basic
    make -f /mnt/samsung_200/sam/kernel/trees/21-rc6/scripts/Makefile.build obj=Documentation/DocBook mandocs
    SRCTREE=/mnt/samsung_200/sam/kernel/trees/21-rc6/ /mnt/samsung_200/sam/kernel/trees/21-rc6/build/scripts/basic/docproc doc /mnt/samsung_200/sam/kernel/trees/21-rc6/Documentation/DocBook/wanbook.tmpl >Documentation/DocBook/wanbook.xml
    if grep -q refentry Documentation/DocBook/wanbook.xml; then xmlto man -m /mnt/samsung_200/sam/kernel/trees/21-rc6/Documentation/DocBook/stylesheet.xsl -o Documentation/DocBook/man Documentation/DocBook/wanbook.xml ; gzip -f Documentation/DocBook/man/*.9; fi
    Note: meta version: No productnumber or alternative sppp_close
    Note: meta version: No refmiscinfo@class=version sppp_close
    Note: Writing sppp_close.9
    Note: meta version: No productnumber or alternative sppp_open
    Note: meta version: No refmiscinfo@class=version sppp_open

    by adding a RefMiscInfo xml tag in the form of the current kernel version
    to the function, struct and enum definitions in files included by
    kernel-doc when building 'mandocs'. However, the version string appears
    truncated on the manpage due to some constraints in the xml DTD for the man
    header, I believe, for the troff output is truncated too.

    Signed-off-by: Borislav Petkov
    Cc: "Randy.Dunlap"
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Borislav Petkov
     
  • Johannes Berg reported that struct names are not highlighted
    (bold, italic, etc.) in html kernel-doc output. (Also not in
    text-mode output, but I don't see that changing.)

    This patch adds the following:
    - highlight struct names in html output mode
    - highlight environment var. names in html output mode
    - indent struct fields in the original struct layout

    Signed-off-by: Randy Dunlap
    Cc: Johannes Berg
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Randy Dunlap
     
  • In a different approach here's a patch that handles the special case of
    composite arithmetic expressions in array size initializers. With it,
    prior to pushing the split strings on the @first_arg array, I split the
    keywords before the array name as before and then keep the array name along
    with the subscript expression as a single whole element which gets pushed
    last. In this manner, kernel-doc produces correct output without removing
    whitespaces which makes the array subscripts unreadable in the docs.

    Signed-off-by: Borislav Petkov
    Signed-off-by: Randy Dunlap
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Borislav Petkov
     
  • Whitespace cleanup only: convert some series of spaces to tabs.

    Signed-off-by: Randy Dunlap
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Randy Dunlap
     
  • This patch is add white list into modpost.c for some functions and
    ia64's section to fix section mismatchs.

    sparse_index_alloc() and zone_wait_table_init() calls bootmem allocator
    at boot time, and kmalloc/vmalloc at hotplug time. If config
    memory hotplug is on, there are references of bootmem allocater(init text)
    from them (normal text). This is cause of section mismatch.

    Bootmem is called by many functions and it must be
    used only at boot time. I think __init of them should keep for
    section mismatch check. So, I would like to register sparse_index_alloc()
    and zone_wait_table_init() into white list.

    In addition, ia64's .machvec section is function table of some platform
    dependent code. It is mixture of .init.text and normal text. These
    reference of __init functions are valid too.

    Signed-off-by: Yasunori Goto
    Cc: Sam Ravnborg
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Yasunori Goto
     

08 May, 2007

1 commit

  • This adds support for the Analog Devices Blackfin processor architecture, and
    currently supports the BF533, BF532, BF531, BF537, BF536, BF534, and BF561
    (Dual Core) devices, with a variety of development platforms including those
    avaliable from Analog Devices (BF533-EZKit, BF533-STAMP, BF537-STAMP,
    BF561-EZKIT), and Bluetechnix! Tinyboards.

    The Blackfin architecture was jointly developed by Intel and Analog Devices
    Inc. (ADI) as the Micro Signal Architecture (MSA) core and introduced it in
    December of 2000. Since then ADI has put this core into its Blackfin
    processor family of devices. The Blackfin core has the advantages of a clean,
    orthogonal,RISC-like microprocessor instruction set. It combines a dual-MAC
    (Multiply/Accumulate), state-of-the-art signal processing engine and
    single-instruction, multiple-data (SIMD) multimedia capabilities into a single
    instruction-set architecture.

    The Blackfin architecture, including the instruction set, is described by the
    ADSP-BF53x/BF56x Blackfin Processor Programming Reference
    http://blackfin.uclinux.org/gf/download/frsrelease/29/2549/Blackfin_PRM.pdf

    The Blackfin processor is already supported by major releases of gcc, and
    there are binary and source rpms/tarballs for many architectures at:
    http://blackfin.uclinux.org/gf/project/toolchain/frs There is complete
    documentation, including "getting started" guides available at:
    http://docs.blackfin.uclinux.org/ which provides links to the sources and
    patches you will need in order to set up a cross-compiling environment for
    bfin-linux-uclibc

    This patch, as well as the other patches (toolchain, distribution,
    uClibc) are actively supported by Analog Devices Inc, at:
    http://blackfin.uclinux.org/

    We have tested this on LTP, and our test plan (including pass/fails) can
    be found at:
    http://docs.blackfin.uclinux.org/doku.php?id=testing_the_linux_kernel

    [m.kozlowski@tuxland.pl: balance parenthesis in blackfin header files]
    Signed-off-by: Bryan Wu
    Signed-off-by: Mariusz Kozlowski
    Signed-off-by: Aubrey Li
    Signed-off-by: Jie Zhang
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Bryan Wu
     

07 May, 2007

1 commit

  • * git://git.kernel.org/pub/scm/linux/kernel/git/sam/kbuild: (38 commits)
    kconfig: fix mconf segmentation fault
    kbuild: enable use of code from a different dir
    kconfig: error out if recursive dependencies are found
    kbuild: scripts/basic/fixdep segfault on pathological string-o-death
    kconfig: correct minor typo in Kconfig warning message.
    kconfig: fix path to modules.txt in Kconfig help
    usr/Kconfig: fix typo
    kernel-doc: alphabetically-sorted entries in index.html of 'htmldocs'
    kbuild: be more explicit on missing .config file
    kbuild: clarify the creation of the LOCALVERSION_AUTO string.
    kbuild: propagate errors from find in scripts/gen_initramfs_list.sh
    kconfig: refer to qt3 if we cannot find qt libraries
    kbuild: handle compressed cpio initramfs-es
    kbuild: ignore section mismatch warning for references from .paravirtprobe to .init.text
    kbuild: remove stale comment in modpost.c
    kbuild/mkuboot.sh: allow spaces in CROSS_COMPILE
    kbuild: fix make mrproper for Documentation/DocBook/man
    kbuild: remove kconfig binaries during make mrproper
    kconfig/menuconfig: do not hardcode '.config'
    kbuild: override build timestamp & version
    ...

    Linus Torvalds
     

06 May, 2007

3 commits


03 May, 2007

2 commits