From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: [RFC: 2.6 patch] kernel/printk.c: remove unused exports
Date: Wed, 28 Jun 2006 18:54:58 +0200 [thread overview]
Message-ID: <20060628165458.GU13915@stusta.de> (raw)
This patch removes the following unused EXPORT_SYMBOL's:
- console_printk
- is_console_locked
- __printk_ratelimit
Signed-off-by: Adrian Bunk <bunk@stusta.de>
---
@Andrew:
If anyone is considered maintainer of this code, please tell me who it
is so that I can send this patch to him instead of you.
This patch was already sent on:
- 22 Jun 2006
- 16 May 2006
- 1 May 2006
- 18 Apr 2006
- 11 Apr 2006
kernel/printk.c | 4 ----
1 file changed, 4 deletions(-)
--- linux-2.6.17-rc1-mm2-full/kernel/printk.c.old 2006-04-11 01:20:32.000000000 +0200
+++ linux-2.6.17-rc1-mm2-full/kernel/printk.c 2006-04-11 01:21:54.000000000 +0200
@@ -52,8 +52,6 @@
DEFAULT_CONSOLE_LOGLEVEL, /* default_console_loglevel */
};
-EXPORT_SYMBOL(console_printk);
-
/*
* Low lever drivers may need that to know if they can schedule in
* their unblank() callback or not. So let's export it.
@@ -728,7 +726,6 @@
{
return console_locked;
}
-EXPORT_SYMBOL(is_console_locked);
/**
* release_console_sem - unlock the console system
@@ -1033,7 +1030,6 @@
spin_unlock_irqrestore(&ratelimit_lock, flags);
return 0;
}
-EXPORT_SYMBOL(__printk_ratelimit);
/* minimum time in jiffies between messages */
int printk_ratelimit_jiffies = 5 * HZ;
next reply other threads:[~2006-06-28 17:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 16:54 Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-22 10:03 [RFC: 2.6 patch] kernel/printk.c: remove unused exports Adrian Bunk
2006-05-16 17:43 Adrian Bunk
2006-05-01 7:11 Adrian Bunk
2006-04-18 15:05 Adrian Bunk
2006-04-11 3:50 Adrian Bunk
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=20060628165458.GU13915@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@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