10 May, 2007

1 commit


09 May, 2007

4 commits

  • 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
     

02 Mar, 2007

1 commit

  • Allow space(s) between "__attribute__" and "((blah))" so that
    kernel-doc does not complain like:

    Warning(/tester/linsrc/linux-2.6.20-git15//kernel/timer.c:939): No description found for parameter 'read_persistent_clock(void'

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

    Randy Dunlap
     

21 Feb, 2007

1 commit


12 Feb, 2007

5 commits

  • Teach kernel-doc to handle functions that look like the new
    pcim_iomap_table(). Fixes this fatal error in scripts/kernel-doc:

    DOCPROC Documentation/DocBook/kernel-api.xml
    Error(/tester/linsrc/linux-2.6.20-git6//drivers/pci/pci.c:1351): cannot understand prototype: 'void __iomem * const * pcim_iomap_table(struct pci_dev *pdev) '
    make[1]: *** [Documentation/DocBook/kernel-api.xml] Error 1
    make: *** [htmldocs] Error 2

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

    Randy Dunlap
     
  • - in man and text mode output, if the function return type is empty (like it
    is for macros), don't print the return type and a following space; this
    fixes an output malalignment;

    - in the function short description, strip leading, trailing, and multiple
    embedded spaces (to one space); this makes function name/description output
    spacing consistent;

    - fix a comment typo;

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

    Randy Dunlap
     
  • Allow whitespace in pointer-to-function
    [accept "(* done)", not just "(*done)"].

    Allow tabs (spaces are already allowed) between "#define" and a macro name.

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

    Randy Dunlap
     
  • In kernel-doc syntax, be a little flexible: allow whitespace between
    a function parameter name and the colon that must follow it, such as:
    @pdev : PCI device to unplug

    (This allows lots of megaraid kernel-doc to work without tons of
    editing.)

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

    Randy Dunlap
     
  • The malformed HTML was generated after switch to XSLTPROC
    from SGML tools. The reference title

    struct x

    is converted into two recursive tags

    struct x

    There is more possible solutions for this problem.
    One can be found at

    http://darkk.livejournal.com/

    The proposed solution is based on suggestion provided by Jiri Kosek.

    Signed-off-by: Pavel Pisa
    Acked-by: Randy Dunlap
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Pavel Pisa
     

23 Dec, 2006

1 commit

  • Make kernel-doc support unnamed (anonymous) structs and unions. There is
    one (union) in include/linux/skbuff.h (inside struct sk_buff) that is
    currently generating a kernel-doc warning, so this fixes that warning.

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

    Randy Dunlap
     

08 Dec, 2006

1 commit

  • Be more careful about function pointer args:
    look for "(...*" instead of just "(".

    This line in include/linux/input.h fools the current kernel-doc script
    into deciding that this is a function pointer:

    unsigned long ffbit[NBITS(FF_MAX)];

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

    Randy Dunlap
     

12 Oct, 2006

2 commits

  • - In parameter descriptions, strip all whitespace between the parameter
    name (e.g., @len) and its description so that the description is
    indented uniformly in text and man page modes. Previously, spaces
    or tabs (which are used for cleaner source code viewing) affected
    the produced output in a negative way.

    Before (man mode):
    to Destination address, in user space.
    from Source address, in kernel space.
    n Number of bytes to copy.

    After (man mode):
    to Destination address, in user space.
    from Source address, in kernel space.
    n Number of bytes to copy.

    - Fix/clarify a few function description comments.

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

    Randy Dunlap
     
  • Drop __inline, __always_inline, and noinline in the produced kernel-doc
    output, similar to other pseudo directives.

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

    Randy Dunlap
     

04 Oct, 2006

1 commit


01 Aug, 2006

1 commit


02 Jul, 2006

2 commits

  • Make output of function descriptions in text mode match contents of 'man'
    mode by adding Name: plus function-short-description ("purpose") and
    changing Function: to Synopsis:.

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

    Randy Dunlap
     
  • Add a space between data type and struct field name in man-mode
    bitfield struct output so that they don't run together.

    For text-mode struct output, print the struct 'purpose' or
    short description (as done in man-mode output).

    For text-mode enum output, print the enum 'purpose' or
    short description (as done in man-mode output).

    For text-mode typedef output, print the typedef 'purpose' or
    short description (as done in man-mode output).

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

    Randy.Dunlap
     

26 Jun, 2006

5 commits

  • kernel-doc struct fields should be consistently called "Members", not
    "Arguments", so switch man-mode output to use "Members" like all of the
    other formats do.

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

    Randy Dunlap
     
  • For kernel-doc output modes of text and man, do not use XML escapes for
    less-than, greater-than, and ampersand characters. I.e., leave the text
    and man output clean and readable.

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

    Randy Dunlap
     
  • When the verbose (-v) option is used with scripts/kernel-doc, this option
    reports when the kernel-doc format is malformed and apparently contains
    function description lines before function parameters. In these cases, the
    kernel-doc script will print something like: Warning(filemap.c:335):
    contents before sections

    I have fixed the problems in mm/filemap.c and added lots of kernel-doc to
    that file (posted to the linux-mm mailing list Mon. 2006-June-12).

    The real goal (as requested by Andrew Morton) is to allow the short
    function description to be more than one line long. This patch is both a
    kernel-doc checker and a tool en route to that goal.

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

    Randy Dunlap
     
  • Fix indentation.
    Quote a brace '{' so that vi won't be fooled by it.

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

    Randy Dunlap
     
  • Drop leading space of kernel-doc section contents.

    "Section" data (contents) are split from the section header
    (e.g., Note: below is a section header:
    * Note: list_empty on entry does not return true after this, the entry is
    * in an undefined state.
    ).

    Currently the data/contents begins with a space and is left that way, which
    causes it to look bad when printed (in text mode; see example below), so
    just remove the leading space.

    Note:

    list_empty on entry does not return true after this, the entry is in an
    undefined state.

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

    Randy Dunlap
     

02 Feb, 2006

3 commits


11 Jan, 2006

1 commit

  • Previously kernel-doc silently ignored missing parameter descriptions for
    preprocessor macros. Now that all such omissions are fixed up we can warn
    about them in kernel-doc to be able to keep it that way.

    Signed-off-by: Martin Waitz
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Martin Waitz
     

14 Nov, 2005

1 commit


14 Jul, 2005

1 commit

  • Current kernel-doc (perl) script generates this warning:
    Use of uninitialized value in concatenation (.) or string at scripts/kernel-doc line 1668.

    So explicitly check for SRCTREE in the ENV before using it,
    and then if it is set, append a '/' to the end of it, otherwise
    the SRCTREE + filename can (will) be missing the intermediate '/'.

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

    Randy Dunlap
     

01 May, 2005

4 commits

  • xmlto uses standared XSLT templates to generate manpages, (x)html pages, and
    XML FO files which can be processed with passivetex. This is much faster than
    using jadetex for everything. This patch also reduces the number of
    kernel-specific scripts that are needed to generate documentation.

    Signed-off-by: Martin Waitz
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Martin Waitz
     
  • Signed-off-by: Martin Waitz
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Rich Walker
     
  • This fix is needed to create valid XML.

    Signed-off-by: Martin Waitz
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Martin Waitz
     
  • I have recompiled Linux kernel 2.6.11.5 documentation for me and our
    university students again. The documentation could be extended for more
    sources which are equipped by structured comments for recent 2.6 kernels. I
    have tried to proceed with that task. I have done that more times from 2.6.0
    time and it gets boring to do same changes again and again. Linux kernel
    compiles after changes for i386 and ARM targets. I have added references to
    some more files into kernel-api book, I have added some section names as well.
    So please, check that changes do not break something and that categories are
    not too much skewed.

    I have changed kernel-doc to accept "fastcall" and "asmlinkage" words reserved
    by kernel convention. Most of the other changes are modifications in the
    comments to make kernel-doc happy, accept some parameters description and do
    not bail out on errors. Changed to @pid in the description, moved some
    #ifdef before comments to correct function to comments bindings, etc.

    You can see result of the modified documentation build at
    http://cmp.felk.cvut.cz/~pisa/linux/lkdb-2.6.11.tar.gz

    Some more sources are ready to be included into kernel-doc generated
    documentation. Sources has been added into kernel-api for now. Some more
    section names added and probably some more chaos introduced as result of quick
    cleanup work.

    Signed-off-by: Pavel Pisa
    Signed-off-by: Martin Waitz
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Pavel Pisa
     

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