linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Rusty Russell <rusty@rustcorp.com.au>, Tejun Heo <tj@kernel.org>
Subject: [PATCH -next] module.h: add stub for is_module_percpu_address
Date: Tue, 30 Mar 2010 10:31:55 -0700	[thread overview]
Message-ID: <4BB2358B.3090800@oracle.com> (raw)
In-Reply-To: <20100330191834.f2009292.sfr@canb.auug.org.au>

From: Randy Dunlap <randy.dunlap@oracle.com>

Fix build for CONFIG_MODULES not enabled by providing a stub
for is_module_percpu_address().

kernel/lockdep.c:605: error: implicit declaration of function 'is_module_percpu_address'

Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
 include/linux/module.h |    5 +++++
 1 file changed, 5 insertions(+)

--- linux-next-20100330.orig/include/linux/module.h
+++ linux-next-20100330/include/linux/module.h
@@ -567,6 +567,11 @@ static inline bool is_module_address(uns
 	return false;
 }
 
+static inline bool is_module_percpu_address(unsigned long addr)
+{
+	return false;
+}
+
 static inline bool is_module_text_address(unsigned long addr)
 {
 	return false;

  reply	other threads:[~2010-03-30 17:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-30  8:18 linux-next: Tree for March 30 Stephen Rothwell
2010-03-30 17:31 ` Randy Dunlap [this message]
2010-03-31  2:34   ` [PATCH -next] module.h: add stub for is_module_percpu_address Tejun Heo
2010-03-31 12:59   ` Rusty Russell
2010-03-30 17:32 ` [PATCH -next] gspca: fix build for INPUT=m or INPUT=n Randy Dunlap
2010-03-30 17:46 ` [PATCH -next] sound: fix patch_realtek printk format Randy Dunlap
2010-03-30 18:03   ` Takashi Iwai

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=4BB2358B.3090800@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=sfr@canb.auug.org.au \
    --cc=tj@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;
as well as URLs for NNTP newsgroup(s).