public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: arch/x86/include/asm/mc146818rtc.h:44:2: error: implicit declaration of function 'this_cpu_read'
Date: Tue, 02 Oct 2012 14:12:00 +0000	[thread overview]
Message-ID: <20121002141200.GA14146@localhost> (raw)

Hi Arnd,

FYI, kernel build failed on

commit: 72e2c3166db31bbb25654be3985ea662fa141d8e  warnings in include/linux/mc146818rtc.h
config: i386-allmodconfig

All error/warnings:

arch/x86/include/asm/mc146818rtc.h:44:17: sparse: undefined identifier 'this_cpu_read'
arch/x86/include/asm/mc146818rtc.h:44:17: sparse: not a function <noident>
In file included from include/linux/mc146818rtc.h:15:0,
                 from arch/x86/kernel/rtc.c:5:
arch/x86/include/asm/mc146818rtc.h: In function 'lock_cmos':
arch/x86/include/asm/mc146818rtc.h:44:2: error: implicit declaration of function 'this_cpu_read' [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
--
In file included from include/linux/mc146818rtc.h:15:0,
                 from drivers/char/mwave/smapi.c:50:
arch/x86/include/asm/mc146818rtc.h: In function 'lock_cmos':
arch/x86/include/asm/mc146818rtc.h:44:2: error: implicit declaration of function 'this_cpu_read' [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors

sparse static analyze warnings:

? arch/x86/include/asm/mc146818rtc.h:44:17: sparse: undefined identifier 'this_cpu_read'
? arch/x86/include/asm/mc146818rtc.h:44:17: sparse: not a function <noident>

vim +44 arch/x86/include/asm/mc146818rtc.h

6ce60b07 include/asm-x86/mc146818rtc.h (Thomas Gleixner 2008-01-30  41) static inline void lock_cmos(unsigned char reg)
6ce60b07 include/asm-x86/mc146818rtc.h (Thomas Gleixner 2008-01-30  42) {
6ce60b07 include/asm-x86/mc146818rtc.h (Thomas Gleixner 2008-01-30  43) 	unsigned long new;
933a4415 include/asm-x86/mc146818rtc.h (Joe Perches     2008-03-23 @44) 	new = ((smp_processor_id() + 1) << 8) | reg;
6ce60b07 include/asm-x86/mc146818rtc.h (Thomas Gleixner 2008-01-30  45) 	for (;;) {
6ce60b07 include/asm-x86/mc146818rtc.h (Thomas Gleixner 2008-01-30  46) 		if (cmos_lock) {
6ce60b07 include/asm-x86/mc146818rtc.h (Thomas Gleixner 2008-01-30  47) 			cpu_relax();
6ce60b07 include/asm-x86/mc146818rtc.h (Thomas Gleixner 2008-01-30  48) 			continue;
6ce60b07 include/asm-x86/mc146818rtc.h (Thomas Gleixner 2008-01-30  49) 		}
6ce60b07 include/asm-x86/mc146818rtc.h (Thomas Gleixner 2008-01-30  50) 		if (__cmpxchg(&cmos_lock, 0, new, sizeof(cmos_lock)) = 0)
6ce60b07 include/asm-x86/mc146818rtc.h (Thomas Gleixner 2008-01-30  51) 			return;
6ce60b07 include/asm-x86/mc146818rtc.h (Thomas Gleixner 2008-01-30  52) 	}

---
0-DAY kernel build testing backend         Open Source Technology Centre
Fengguang Wu, Yuanhan Liu                              Intel Corporation

             reply	other threads:[~2012-10-02 14:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-02 14:12 Fengguang Wu [this message]
2012-10-03 14:15 ` arch/x86/include/asm/mc146818rtc.h:44:2: error: implicit declaration of function 'this_cpu_read' Arnd Bergmann

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=20121002141200.GA14146@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox