From: Adrian Bunk <bunk@kernel.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: [2.6 patch] the scheduled 'time' option removal
Date: Tue, 1 Jan 2008 15:46:56 +0200 [thread overview]
Message-ID: <20080101134656.GG2360@does.not.exist> (raw)
This patch contains the scheduled removal of the 'time' option.
Signed-off-by: Adrian Bunk <bunk@kernel.org>
---
Documentation/feature-removal-schedule.txt | 8 --------
kernel/printk.c | 13 -------------
2 files changed, 21 deletions(-)
c0ea16c447460698c0e85963310c38fa051f0e23
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index 20c4c8b..93aac19 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -233,10 +233,2 @@ Who: Jean Delvare <khali@linux-fr.org>
---------------------------
-
-What: 'time' kernel boot parameter
-When: January 2008
-Why: replaced by 'printk.time=<value>' so that printk timestamps can be
- enabled or disabled as needed
-Who: Randy Dunlap <randy.dunlap@oracle.com>
-
----------------------------
diff --git a/kernel/printk.c b/kernel/printk.c
index a30fe33..296c4ea 100644
--- a/kernel/printk.c
+++ b/kernel/printk.c
@@ -560,15 +560,2 @@ static int printk_time = 0;
module_param_named(time, printk_time, bool, S_IRUGO | S_IWUSR);
-
-static int __init printk_time_setup(char *str)
-{
- if (*str)
- return 0;
- printk_time = 1;
- printk(KERN_NOTICE "The 'time' option is deprecated and "
- "is scheduled for removal in early 2008\n");
- printk(KERN_NOTICE "Use 'printk.time=<value>' instead\n");
- return 1;
-}
-
-__setup("time", printk_time_setup);
next reply other threads:[~2008-01-01 13:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-01 13:46 Adrian Bunk [this message]
2008-01-01 17:53 ` [2.6 patch] the scheduled 'time' option removal Jan Engelhardt
2008-01-01 23:57 ` Adrian Bunk
2008-01-02 2:07 ` Randy Dunlap
2008-01-20 14:02 ` Adrian Bunk
2008-01-20 17:31 ` Randy Dunlap
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=20080101134656.GG2360@does.not.exist \
--to=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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).