From: Anton Blanchard <anton@samba.org>
To: Olof Johansson <olof@lixom.net>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH] Quieten cache information at boot
Date: Sun, 14 Oct 2007 16:03:05 -0500 [thread overview]
Message-ID: <20071014210305.GE26693@kryten> (raw)
In-Reply-To: <20071014201431.GA23002@lixom.net>
Hi,
> Let's just remove it completely. I have yet to see a bug because of it,
> and we have 0x40 byte cache lines.
Yeah I completely support killing it too :)
> If anything, compare firmware setting to cputable one and print a warning.
>
> Should maybe give them loglevels too, since you're touching them? I
> suggest KERN_DEBUG -- if needed it's there in dmesg, and if you need it
> on the console you can just add "debug" to the kernel command line.
I started playing with loglevels but theres some ordering issues since
the options to change loglevel (eg the "debug" boot option) doesnt get
parsed until later in a __setup function.
Anton
next prev parent reply other threads:[~2007-10-14 21:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-14 19:33 [PATCH] Quieten cache information at boot Anton Blanchard
2007-10-14 20:14 ` Olof Johansson
2007-10-14 21:03 ` Anton Blanchard [this message]
2007-10-14 21:18 ` Benjamin Herrenschmidt
2007-10-14 21:17 ` Benjamin Herrenschmidt
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=20071014210305.GE26693@kryten \
--to=anton@samba.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
--cc=paulus@samba.org \
/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).