From: Chen Gang <chengang@emindsoft.com.cn>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, trivial@kernel.org, akpm@linux-foundation.org,
viro@zeniv.linux.org.uk, dhowells@redhat.com,
nicolas.iooss_linux@m4x.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH trivial] include/linux/dcache.h: Cleanup code and comments
Date: Sun, 10 Jan 2016 00:16:12 +0800 [thread overview]
Message-ID: <5691324C.7090400@emindsoft.com.cn> (raw)
In-Reply-To: <201601092136.P1X3ym7N%fengguang.wu@intel.com>
On 1/9/16 21:27, kbuild test robot wrote:
> Hi Chen,
>
> [auto build test WARNING on v4.4-rc8]
> [also build test WARNING on next-20160108]
> [if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
>
> url: https://github.com/0day-ci/linux/commits/chengang-emindsoft-com-cn/include-linux-dcache-h-Cleanup-code-and-comments/20160109-203554
> reproduce: make htmldocs
>
> All warnings (new ones prefixed by >>):
>
>>> include/linux/dcache.h:1: warning: no structured comments found
It looks, we should still reserve "/**" for the comments (my patch use
"/*" instead of "/**").
Thanks.
> include/linux/jbd2.h:439: warning: No description found for parameter 'i_transaction'
> include/linux/jbd2.h:439: warning: No description found for parameter 'i_next_transaction'
> include/linux/jbd2.h:439: warning: No description found for parameter 'i_list'
> include/linux/jbd2.h:439: warning: No description found for parameter 'i_vfs_inode'
> include/linux/jbd2.h:439: warning: No description found for parameter 'i_flags'
> include/linux/jbd2.h:495: warning: No description found for parameter 'h_rsv_handle'
> include/linux/jbd2.h:495: warning: No description found for parameter 'h_reserved'
> include/linux/jbd2.h:495: warning: No description found for parameter 'h_type'
> include/linux/jbd2.h:495: warning: No description found for parameter 'h_line_no'
> include/linux/jbd2.h:495: warning: No description found for parameter 'h_start_jiffies'
> include/linux/jbd2.h:495: warning: No description found for parameter 'h_requested_credits'
> include/linux/jbd2.h:495: warning: No description found for parameter 'h_lockdep_map'
> include/linux/jbd2.h:1038: warning: No description found for parameter 'j_chkpt_bhs[JBD2_NR_BATCH]'
> include/linux/jbd2.h:1038: warning: No description found for parameter 'j_devname[BDEVNAME_SIZE+24]'
> include/linux/jbd2.h:1038: warning: No description found for parameter 'j_average_commit_time'
> include/linux/jbd2.h:1038: warning: No description found for parameter 'j_min_batch_time'
> include/linux/jbd2.h:1038: warning: No description found for parameter 'j_max_batch_time'
> include/linux/jbd2.h:1038: warning: No description found for parameter 'j_commit_callback'
> include/linux/jbd2.h:1038: warning: No description found for parameter 'j_failed_commit'
> include/linux/jbd2.h:1038: warning: No description found for parameter 'j_chksum_driver'
> include/linux/jbd2.h:1038: warning: No description found for parameter 'j_csum_seed'
> include/linux/jbd2.h:1038: warning: Excess struct/union/enum/typedef member 'j_history' description in 'journal_s'
> include/linux/jbd2.h:1038: warning: Excess struct/union/enum/typedef member 'j_history_max' description in 'journal_s'
> include/linux/jbd2.h:1038: warning: Excess struct/union/enum/typedef member 'j_history_cur' description in 'journal_s'
> fs/jbd2/transaction.c:429: warning: No description found for parameter 'rsv_blocks'
> fs/jbd2/transaction.c:429: warning: No description found for parameter 'gfp_mask'
> fs/jbd2/transaction.c:429: warning: No description found for parameter 'type'
> fs/jbd2/transaction.c:429: warning: No description found for parameter 'line_no'
> fs/jbd2/transaction.c:505: warning: No description found for parameter 'type'
> fs/jbd2/transaction.c:505: warning: No description found for parameter 'line_no'
> fs/jbd2/transaction.c:635: warning: No description found for parameter 'gfp_mask'
>
> vim +1 include/linux/dcache.h
>
> ^1da177e4 Linus Torvalds 2005-04-16 @1 #ifndef __LINUX_DCACHE_H
> ^1da177e4 Linus Torvalds 2005-04-16 2 #define __LINUX_DCACHE_H
> ^1da177e4 Linus Torvalds 2005-04-16 3
> 60063497a Arun Sharma 2011-07-26 4 #include <linux/atomic.h>
> ^1da177e4 Linus Torvalds 2005-04-16 5 #include <linux/list.h>
> 82524746c Franck Bui-Huu 2008-05-12 6 #include <linux/rculist.h>
> ceb5bdc2d Nick Piggin 2011-01-07 7 #include <linux/rculist_bl.h>
> ^1da177e4 Linus Torvalds 2005-04-16 8 #include <linux/spinlock.h>
> 31e6b01f4 Nick Piggin 2011-01-07 9 #include <linux/seqlock.h>
>
> :::::: The code at line 1 was first introduced by commit
> :::::: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 Linux-2.6.12-rc2
>
> :::::: TO: Linus Torvalds <torvalds@ppc970.osdl.org>
> :::::: CC: Linus Torvalds <torvalds@ppc970.osdl.org>
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
>
--
Chen Gang (陈刚)
Open, share, and attitude like air, water, and life which God blessed
prev parent reply other threads:[~2016-01-09 16:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-09 12:33 [PATCH trivial] include/linux/dcache.h: Cleanup code and comments chengang
2016-01-09 13:27 ` kbuild test robot
2016-01-09 16:16 ` Chen Gang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5691324C.7090400@emindsoft.com.cn \
--to=chengang@emindsoft.com.cn \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=nicolas.iooss_linux@m4x.org \
--cc=trivial@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.