From: Rene Herman <rene.herman@gmail.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
lkml <linux-kernel@vger.kernel.org>,
akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH] add "notime" boot option
Date: Thu, 24 May 2007 06:54:43 +0200 [thread overview]
Message-ID: <46551A93.6050801@gmail.com> (raw)
In-Reply-To: <20070523135513.b3573f52.randy.dunlap@oracle.com>
On 05/23/2007 10:55 PM, Randy Dunlap wrote:
>>>> That's a good source of confusion. To me, "notime" means something
>>>> like "don't bother calculating time", instead of the proposed
>>>> behavior. Can't it be something like 'nologts' (no log timestamps)
>>>> or nots or notimestamps or nologtime instead
>>>
>>> "nologtime" is OK with me. or does it confuse people in a different
>>> way? Anyone else?
>>
>> The CONFIG option is called CONFIG_PRINTK_TIME. How about "noprintktime"? At
>> least nicely to the point...
>
> Actually I'm concerned about total kernel command line length,
> so using option names that are "long" when short will do is not good IMO.
>
> I.e., I can easily overflow a 255-byte command line length buffer,
> so Shorter is Better.
Okay. I would by the way not be against turning the timestamping off by
default and turning it _on_ with a "timestamps" or "logtime" or whatever
option. The information is sometimes handy for seeing the (clustering of)
event times so I've been compiling it in for a while on some boxes but in
the majority case for me it's noise taking up printk real estate...
Rene.
next prev parent reply other threads:[~2007-05-24 4:57 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 [this message]
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
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=46551A93.6050801@gmail.com \
--to=rene.herman@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--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