From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [dynticks:nohz/printk 5/5] kernel/printk.c:1999:2: error: implicit declaration of function 'arch_irq
Date: Sat, 13 Oct 2012 00:04:32 +0000 [thread overview]
Message-ID: <20121013000432.GB27431@localhost> (raw)
Hi Frederic,
FYI, kernel build failed on
tree: git://github.com/fweisbec/linux-dynticks.git nohz/printk
head: f72ce6fbecebcf9faeaa740754ac71474758c1f6
commit: f72ce6fbecebcf9faeaa740754ac71474758c1f6 [5/5] printk: Wake up klogd with irq_work on nohz CPU
config: sparc64-defconfig # make ARCH=sparc64 defconfig
All error/warnings:
kernel/printk.c: In function 'wake_up_klogd_nohz':
kernel/printk.c:1999:2: error: implicit declaration of function 'arch_irq_work_use_tick' [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
vim +1999 kernel/printk.c
f72ce6fb Frederic Weisbecker 2012-10-12 1993 {
f72ce6fb Frederic Weisbecker 2012-10-12 1994 /*
f72ce6fb Frederic Weisbecker 2012-10-12 1995 * If irq work is not itself implemented using the tick
f72ce6fb Frederic Weisbecker 2012-10-12 1996 * it's a safe and fast way to wake up the reader.
f72ce6fb Frederic Weisbecker 2012-10-12 1997 */
f72ce6fb Frederic Weisbecker 2012-10-12 1998 #ifdef CONFIG_IRQ_WORK
f72ce6fb Frederic Weisbecker 2012-10-12 @1999 if (!arch_irq_work_use_tick()) {
f72ce6fb Frederic Weisbecker 2012-10-12 2000 static struct irq_work klogd_irq_work = {
f72ce6fb Frederic Weisbecker 2012-10-12 2001 .func = wake_klogd_irq_work
f72ce6fb Frederic Weisbecker 2012-10-12 2002 };
---
0-DAY kernel build testing backend Open Source Technology Center
Fengguang Wu, Yuanhan Liu Intel Corporation
reply other threads:[~2012-10-13 0:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20121013000432.GB27431@localhost \
--to=fengguang.wu@intel.com \
--cc=kernel-janitors@vger.kernel.org \
/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.