From: Andrew Morton <akpm@linux-foundation.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
rene.herman@gmail.com, mjt@tls.msk.ru,
Jan Engelhardt <jengelh@linux01.gwdg.de>
Subject: Re: [PATCH] use printk.time option, drop time/notime
Date: Tue, 29 May 2007 13:07:05 -0700 [thread overview]
Message-ID: <20070529130705.fdf43e4b.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070524171535.329ea2c0.randy.dunlap@oracle.com>
On Thu, 24 May 2007 17:15:35 -0700
Randy Dunlap <randy.dunlap@oracle.com> wrote:
> Allow printk_time to be enabled or disabled at boot time.
> Previously it could be enabled only, but not disabled.
>
> Change printk_time from an int to a bool since that's what it is.
> Make its logical (exposed) name just be "time" (was "printk_time").
>
> Note: Changes kernel boot option syntax from "time" to "printk.time=value".
That's going to break a *lot* of people's setups - timestamping appears
to be very popular. We will get sad emails from people.
If we're going to do this then I'm afraid we should retain the `time='
thing for a while and add a this-is-going-away printk to it.
next prev parent reply other threads:[~2007-05-29 20:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 19:09 [PATCH] add "notime" boot option Randy Dunlap
2007-05-22 19:40 ` Dave Jones
2007-05-22 20:00 ` Randy Dunlap
2007-05-23 11:03 ` Michael Tokarev
2007-05-23 17:04 ` Randy Dunlap
2007-05-23 19:15 ` Rene Herman
2007-05-23 20:55 ` Randy Dunlap
2007-05-24 4:54 ` Rene Herman
2007-05-24 5:08 ` Randy Dunlap
2007-05-24 5:11 ` Rene Herman
2007-05-24 6:29 ` Rene Herman
2007-05-24 16:13 ` Jan Engelhardt
2007-05-24 16:24 ` Randy Dunlap
2007-05-24 16:33 ` Jan Engelhardt
2007-05-25 0:15 ` [PATCH] use printk.time option, drop time/notime Randy Dunlap
2007-05-29 20:07 ` Andrew Morton [this message]
2007-05-29 21:28 ` Jan Engelhardt
2007-05-30 18:37 ` [PATCH v3] add printk.time option, deprecate 'time' 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=20070529130705.fdf43e4b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=randy.dunlap@oracle.com \
--cc=rene.herman@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.