From: kbuild test robot <lkp@intel.com>
To: akash.goel@intel.com
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, viro@zeniv.linux.org.uk,
Akash Goel <akash.goel@intel.com>,
Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>,
Tom Zanussi <tzanussi@gmail.com>,
Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [PATCH v3] relay: Add global mode support for buffer-only channels
Date: Wed, 13 Jul 2016 16:30:42 +0800 [thread overview]
Message-ID: <201607131634.TH6GcXHQ%fengguang.wu@intel.com> (raw)
In-Reply-To: <1468395556-31986-1-git-send-email-akash.goel@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2150 bytes --]
Hi,
[auto build test WARNING on v4.7-rc7]
[also build test WARNING on next-20160712]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/akash-goel-intel-com/relay-Add-global-mode-support-for-buffer-only-channels/20160713-153432
reproduce: make htmldocs
All warnings (new ones prefixed by >>):
lib/crc32.c:148: warning: No description found for parameter 'tab)[256]'
lib/crc32.c:148: warning: Excess function parameter 'tab' description in 'crc32_le_generic'
lib/crc32.c:293: warning: No description found for parameter 'tab)[256]'
lib/crc32.c:293: warning: Excess function parameter 'tab' description in 'crc32_be_generic'
lib/crc32.c:1: warning: no structured comments found
>> kernel/relay.c:572: warning: bad line:
>> kernel/relay.c:572: warning: bad line:
vim +572 kernel/relay.c
556
557 /**
558 * relay_open - create a new relay channel
559 * @base_filename: base name of files to create, %NULL for buffering only
560 * @parent: dentry of parent directory, %NULL for root directory or buffer
561 * @subbuf_size: size of sub-buffers
562 * @n_subbufs: number of sub-buffers
563 * @cb: client callback functions
564 * @private_data: user-defined data
565 *
566 * Returns channel pointer if successful, %NULL otherwise.
567 *
568 * Creates a channel buffer for each cpu using the sizes and
569 * attributes specified. The created channel buffer files
570 * will be named base_filename0...base_filenameN-1. File
571 * permissions will be %S_IRUSR.
> 572
573 * If opening a buffer (@parent = NULL) that you later wish to register
574 * in a filesystem, call relay_late_setup_files() once the @parent dentry
575 * is available.
576 */
577 struct rchan *relay_open(const char *base_filename,
578 struct dentry *parent,
579 size_t subbuf_size,
580 size_t n_subbufs,
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 6370 bytes --]
next prev parent reply other threads:[~2016-07-13 8:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-03 16:15 [PATCH] " akash.goel
2016-07-04 8:00 ` Chris Wilson
2016-07-04 13:03 ` Goel, Akash
2016-07-11 7:17 ` [PATCH v2] " akash.goel
2016-07-11 20:17 ` Andrew Morton
2016-07-12 9:24 ` Chris Wilson
2016-07-12 12:50 ` Goel, Akash
2016-07-12 13:01 ` Chris Wilson
2016-07-12 13:24 ` Goel, Akash
2016-07-12 19:51 ` Andrew Morton
2016-07-13 7:39 ` [PATCH v3] " akash.goel
2016-07-13 8:30 ` kbuild test robot [this message]
2016-07-13 10:09 ` [PATCH v4] " akash.goel
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=201607131634.TH6GcXHQ%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akash.goel@intel.com \
--cc=akpm@linux-foundation.org \
--cc=chris@chris-wilson.co.uk \
--cc=eduard.munteanu@linux360.ro \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tzanussi@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®