Subject: Re: linux-next: Tree for Mar 15 (staging/android/ram_console.c)

From: Greg Kroah-Hartman <[email-masked]>
Date: Thu, 15 Mar 2012 14:03:33 -0700

On Thu, Mar 15, 2012 at 08:58:02AM -0700, Randy Dunlap wrote:
> On 03/15/2012 12:59 AM, Stephen Rothwell wrote:
> 
> > Hi all,
> > 
> > News: the build system (see below) has had its toolchains for most
> > architectures updated to gcc 4.6.3.  People might like to check the build
> > results and consider if this change has caused any problems.  There are
> > also a number of architectures that are building today for the first
> > time.  Thanks to Tony Breeds for his efforts in providing toolchains.
> > 
> > Changes since 20120314:
> 
> 
> 
> on x86_64 when CONFIG_PRINTK is not enabled:
> 
> 
> drivers/staging/android/ram_console.c:99:6: error: 'dmesg_restrict' undeclared (first use in this function)

This patch should solve this, right?

diff --git a/drivers/staging/android/ram_console.c b/drivers/staging/android/ram_console.c
index 2918bc1..ce140ff 100644
--- a/drivers/staging/android/ram_console.c
+++ b/drivers/staging/android/ram_console.c
@@ -85,6 +85,10 @@ static int __init ram_console_module_init(void)
 	return platform_driver_probe(&ram_console_driver, ram_console_probe);
 }
 
+#ifndef CONFIG_PRINTK
+#define dmesg_restrict	0
+#endif
+
 static ssize_t ram_console_read_old(struct file *file, char __user *buf,
 				    size_t len, loff_t *offset)
 {