From: kbuild test robot <lkp@intel.com>
To: akash.goel@intel.com
Cc: kbuild-all@01.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Tom Zanussi <tzanussi@gmail.com>,
Chris Wilson <chris@chris-wilson.co.uk>,
Tvrtko Ursulin <tvrtko.ursulin@intel.com>,
Akash Goel <akash.goel@intel.com>
Subject: Re: [PATCH] relay: Use irq_work instead of plain timer for deferred wakeup
Date: Fri, 2 Sep 2016 18:49:19 +0800 [thread overview]
Message-ID: <201609021820.12FLQ7f9%fengguang.wu@intel.com> (raw)
In-Reply-To: <1472807144-26704-1-git-send-email-akash.goel@intel.com>
[-- Attachment #1: Type: text/plain, Size: 3719 bytes --]
Hi Peter,
[auto build test WARNING on next-20160825]
[cannot apply to linus/master linux/master v4.8-rc4 v4.8-rc3 v4.8-rc2 v4.8-rc4]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
[Suggest to use git(>=2.9.0) format-patch --base=<commit> (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on]
[Check https://git-scm.com/docs/git-format-patch for more information]
url: https://github.com/0day-ci/linux/commits/akash-goel-intel-com/relay-Use-irq_work-instead-of-plain-timer-for-deferred-wakeup/20160902-165512
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:336: warning: No description found for parameter 'work'
>> kernel/relay.c:336: warning: Excess function parameter 'data' description in 'wakeup_readers'
>> kernel/relay.c:336: warning: No description found for parameter 'work'
>> kernel/relay.c:336: warning: Excess function parameter 'data' description in 'wakeup_readers'
vim +/work +336 kernel/relay.c
b86ff981a Jens Axboe 2006-03-23 320 /* relay channel default callbacks */
b86ff981a Jens Axboe 2006-03-23 321 static struct rchan_callbacks default_channel_callbacks = {
b86ff981a Jens Axboe 2006-03-23 322 .subbuf_start = subbuf_start_default_callback,
b86ff981a Jens Axboe 2006-03-23 323 .buf_mapped = buf_mapped_default_callback,
b86ff981a Jens Axboe 2006-03-23 324 .buf_unmapped = buf_unmapped_default_callback,
b86ff981a Jens Axboe 2006-03-23 325 .create_buf_file = create_buf_file_default_callback,
b86ff981a Jens Axboe 2006-03-23 326 .remove_buf_file = remove_buf_file_default_callback,
b86ff981a Jens Axboe 2006-03-23 327 };
b86ff981a Jens Axboe 2006-03-23 328
b86ff981a Jens Axboe 2006-03-23 329 /**
b86ff981a Jens Axboe 2006-03-23 330 * wakeup_readers - wake up readers waiting on a channel
9a9136e27 Linus Torvalds 2007-05-09 331 * @data: contains the channel buffer
b86ff981a Jens Axboe 2006-03-23 332 *
60538b154 Peter Zijlstra 2016-09-02 333 * This is the function used to defer reader waking
b86ff981a Jens Axboe 2006-03-23 334 */
60538b154 Peter Zijlstra 2016-09-02 335 static void wakeup_readers(struct irq_work *work)
b86ff981a Jens Axboe 2006-03-23 @336 {
60538b154 Peter Zijlstra 2016-09-02 337 struct rchan_buf *buf = container_of(work, struct rchan_buf, wakeup_work);
b86ff981a Jens Axboe 2006-03-23 338 wake_up_interruptible(&buf->read_wait);
b86ff981a Jens Axboe 2006-03-23 339 }
b86ff981a Jens Axboe 2006-03-23 340
b86ff981a Jens Axboe 2006-03-23 341 /**
b86ff981a Jens Axboe 2006-03-23 342 * __relay_reset - reset a channel buffer
b86ff981a Jens Axboe 2006-03-23 343 * @buf: the channel buffer
b86ff981a Jens Axboe 2006-03-23 344 * @init: 1 if this is a first-time initialization
:::::: The code at line 336 was first introduced by commit
:::::: b86ff981a8252d83d6a7719ae09f3a05307e3592 [PATCH] relay: migrate from relayfs to a generic relay API
:::::: TO: Jens Axboe <axboe@suse.de>
:::::: CC: Jens Axboe <axboe@suse.de>
---
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: 6443 bytes --]
next prev parent reply other threads:[~2016-09-02 10:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 9:05 akash.goel
2016-09-02 10:49 ` kbuild test robot [this message]
2016-09-03 12:41 ` [PATCH v2] " 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=201609021820.12FLQ7f9%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=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tvrtko.ursulin@intel.com \
--cc=tzanussi@gmail.com \
/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®