From: kbuild test robot <lkp@intel.com>
To: Weongyo Jeong <weongyo.linux@gmail.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org, linux-scsi@vger.kernel.org,
Weongyo Jeong <weongyo.linux@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Mike Marciniszyn <infinipath@intel.com>,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH v1 2/2] genirq: support multiple IRQ notifier.
Date: Sat, 26 Mar 2016 01:05:01 +0800 [thread overview]
Message-ID: <201603260102.KVPvkrJK%fengguang.wu@intel.com> (raw)
In-Reply-To: <150f84b627280fa9d4397e6a4cdb5d096bef70bd.1458920770.git.weongyo.linux@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2975 bytes --]
Hi Weongyo,
[auto build test WARNING on tip/irq/core]
[also build test WARNING on v4.5 next-20160324]
[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/Weongyo-Jeong/genirq-support-multiple-IRQ-notifier/20160325-235708
reproduce: make htmldocs
All warnings (new ones prefixed by >>):
>> include/linux/interrupt.h:224: warning: No description found for parameter 'list'
kernel/irq/handle.c:1: warning: no structured comments found
vim +/list +224 include/linux/interrupt.h
f0ba3d05c Eyal Perry 2014-05-20 208 * @kref: Reference count, for internal use
f0ba3d05c Eyal Perry 2014-05-20 209 * @work: Work item, for internal use
f0ba3d05c Eyal Perry 2014-05-20 210 * @notify: Function to be called on change. This will be
f0ba3d05c Eyal Perry 2014-05-20 211 * called in process context.
f0ba3d05c Eyal Perry 2014-05-20 212 * @release: Function to be called on release. This will be
f0ba3d05c Eyal Perry 2014-05-20 213 * called in process context. Once registered, the
f0ba3d05c Eyal Perry 2014-05-20 214 * structure must only be freed when this function is
f0ba3d05c Eyal Perry 2014-05-20 215 * called or later.
f0ba3d05c Eyal Perry 2014-05-20 216 */
f0ba3d05c Eyal Perry 2014-05-20 217 struct irq_affinity_notify {
f0ba3d05c Eyal Perry 2014-05-20 218 unsigned int irq;
f0ba3d05c Eyal Perry 2014-05-20 219 struct kref kref;
f0ba3d05c Eyal Perry 2014-05-20 220 struct work_struct work;
f0ba3d05c Eyal Perry 2014-05-20 221 void (*notify)(struct irq_affinity_notify *, const cpumask_t *mask);
f0ba3d05c Eyal Perry 2014-05-20 222 void (*release)(struct kref *ref);
3fb671e48 Weongyo Jeong 2016-03-25 223 struct list_head list;
f0ba3d05c Eyal Perry 2014-05-20 @224 };
f0ba3d05c Eyal Perry 2014-05-20 225
0244ad004 Martin Schwidefsky 2013-08-30 226 #if defined(CONFIG_SMP)
d7b906897 Russell King 2008-04-17 227
d036e67b4 Rusty Russell 2009-01-01 228 extern cpumask_var_t irq_default_affinity;
184047567 Max Krasnyansky 2008-05-29 229
01f8fa4f0 Thomas Gleixner 2014-04-16 230 /* Internal implementation. Use the helpers below */
01f8fa4f0 Thomas Gleixner 2014-04-16 231 extern int __irq_set_affinity(unsigned int irq, const struct cpumask *cpumask,
01f8fa4f0 Thomas Gleixner 2014-04-16 232 bool force);
:::::: The code at line 224 was first introduced by commit
:::::: f0ba3d05c9c647ab42ed6a0dbdfdeae42bfbd6de genirq: Provide !SMP stub for irq_set_affinity_notifier()
:::::: TO: Eyal Perry <eyalpe@mellanox.com>
:::::: CC: Thomas Gleixner <tglx@linutronix.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: 6226 bytes --]
next prev parent reply other threads:[~2016-03-25 17:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 15:51 [PATCH v1 0/2] " Weongyo Jeong
2016-03-25 15:51 ` [PATCH v1 1/2] genirq: clean up for irq_set_affinity_notifier() Weongyo Jeong
2016-03-25 15:51 ` [PATCH v1 2/2] genirq: support multiple IRQ notifier Weongyo Jeong
2016-03-25 17:05 ` kbuild test robot [this message]
2016-03-25 18:58 ` kbuild test robot
2016-03-25 19:32 ` [PATCH v1 0/2] " Christoph Hellwig
2016-03-25 20:49 ` Thomas Gleixner
2016-03-28 18:19 ` Weongyo Jeong
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=201603260102.KVPvkrJK%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=infinipath@intel.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=tglx@linutronix.de \
--cc=weongyo.linux@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®