From: Dave Jones <davej@redhat.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>, akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH] add "notime" boot option
Date: Tue, 22 May 2007 15:40:30 -0400 [thread overview]
Message-ID: <20070522194030.GF12157@redhat.com> (raw)
In-Reply-To: <20070522120938.db67f1e9.randy.dunlap@oracle.com>
On Tue, May 22, 2007 at 12:09:38PM -0700, Randy Dunlap wrote:
> --- linux-2622-rc2.orig/kernel/printk.c
> +++ linux-2622-rc2/kernel/printk.c
> @@ -458,9 +458,17 @@ static int __init printk_time_setup(char
> printk_time = 1;
> return 1;
> }
> -
> __setup("time", printk_time_setup);
>
> +static int __init printk_notime_setup(char *str)
> +{
> + if (*str)
> + return 0;
> + printk_time = 0;
> + return 1;
> +}
> +__setup("notime", printk_notime_setup);
> +
> __attribute__((weak)) unsigned long long printk_clock(void)
> {
> return sched_clock();
Not disagreeing with the patch, but I wonder if it'd be a net win
if we had a helper that would replace the zillion instances
of "set this variable to a 0/1 depending if its prefixed with 'no'"
with 1-2 lines.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2007-05-22 19:41 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 [this message]
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
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=20070522194030.GF12157@redhat.com \
--to=davej@redhat.com \
--cc=akpm@linux-foundation.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