From: Andrew Morton <akpm@osdl.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: dtor_core@ameritech.net, karim@opersys.com,
akropel1@rochester.rr.com, linux-kernel@vger.kernel.org,
tim.bird@am.sony.com, celinux-dev@tree.celinuxforum.org,
tpoynor@mvista.com
Subject: Re: [PATCH] preset loops_per_jiffy for faster booting
Date: Sun, 11 Jul 2004 00:51:56 -0700 [thread overview]
Message-ID: <20040711005156.1d6558dd.akpm@osdl.org> (raw)
In-Reply-To: <Pine.GSO.4.58.0407110945010.3013@waterleaf.sonytel.be>
Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>
> On Sat, 10 Jul 2004, Andrew Morton wrote:
> > Dmitry Torokhov <dtor_core@ameritech.net> wrote:
> > >
> > > I am no longer question presence of the code in the kernel, I just don't like
> > > the message...
> >
> > yup, we shouldn't have the friendly message.
>
> Just add the appropriate KERN_*, so it's not displayed by default, and people
> who want it can look it up in syslog.
Oh crap, sorry. I just worked out what the darn printk is for. Yes, it's
legit. Let's just print the bogomips and loops_per_jiffy on the same line.
next prev parent reply other threads:[~2004-07-11 7:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-09 19:25 [PATCH] preset loops_per_jiffy for faster booting Tim Bird
2004-07-09 22:24 ` Adam Kropelin
2004-07-09 23:35 ` Adam Kropelin
2004-07-10 0:20 ` Tim Bird
2004-07-10 2:01 ` Adam Kropelin
2004-07-10 2:01 ` Todd Poynor
2004-07-10 15:42 ` Adam Kropelin
2004-07-10 14:41 ` [Celinux-dev] " Geert Uytterhoeven
2004-07-10 15:22 ` Adam Kropelin
2004-07-10 15:54 ` Adam Kropelin
2004-07-10 18:28 ` Adam Kropelin
2004-07-10 18:19 ` Dmitry Torokhov
2004-07-10 20:14 ` Adam Kropelin
2004-07-11 1:25 ` Andrew Morton
2004-07-11 3:44 ` Adam Kropelin
2004-07-11 4:38 ` Andrew Morton
2004-07-12 17:31 ` Tim Bird
2004-07-11 4:51 ` Dmitry Torokhov
2004-07-11 4:58 ` Karim Yaghmour
2004-07-11 5:19 ` Dmitry Torokhov
2004-07-11 5:27 ` Andrew Morton
2004-07-11 7:46 ` Geert Uytterhoeven
2004-07-11 7:51 ` Andrew Morton [this message]
2004-07-11 13:41 ` Adam Kropelin
2004-07-12 18:52 ` Tim Bird
2004-07-12 19:32 ` Adam Kropelin
2004-07-12 22:41 ` Tim Bird
2004-07-13 19:24 ` Bartlomiej Zolnierkiewicz
2004-07-12 17:50 ` Tim Bird
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=20040711005156.1d6558dd.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=akropel1@rochester.rr.com \
--cc=celinux-dev@tree.celinuxforum.org \
--cc=dtor_core@ameritech.net \
--cc=geert@linux-m68k.org \
--cc=karim@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.bird@am.sony.com \
--cc=tpoynor@mvista.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.