From: Keith Owens <kaos@ocs.com.au>
To: Jesper Juhl <juhl@eisenstein.dk>
Cc: linux-kernel@vger.kernel.org, linux-ia64@linuxia64.org
Subject: Re: console_loglevel is broken on ia64
Date: Wed, 17 Oct 2001 23:53:01 +1000 [thread overview]
Message-ID: <3145.1003326781@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Wed, 17 Oct 2001 15:39:06 +0200." <3BCD89FA.6050209@eisenstein.dk>
On Wed, 17 Oct 2001 15:39:06 +0200,
Jesper Juhl <juhl@eisenstein.dk> wrote:
>Keith Owens wrote:
>> kernel/printk.c has this abomination.
>> int console_loglevel = DEFAULT_CONSOLE_LOGLEVEL;
>> int default_message_loglevel = DEFAULT_MESSAGE_LOGLEVEL;
>> int minimum_console_loglevel = MINIMUM_CONSOLE_LOGLEVEL;
>> int default_console_loglevel = DEFAULT_CONSOLE_LOGLEVEL;
>> Does anybody fancy a small project to clean up these variables?
>
>I would like to give it a try. Seems like a good little project for one
>who is trying to learn his way around the kernel :)
Good, I was hoping for somebody who wanted to get started on the
kernel. It's all yours, unless somebody else does a patch first.
Ensure that you find all references to these variables and make them
all use the common #define, instead of random files declaring the
variables themselves. Check all architectures as well.
next prev parent reply other threads:[~2001-10-17 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-17 13:25 console_loglevel is broken on ia64 Keith Owens
2001-10-17 13:39 ` Jesper Juhl
2001-10-17 13:53 ` Keith Owens [this message]
2001-10-17 15:00 ` Geert Uytterhoeven
2001-10-17 15:29 ` 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=3145.1003326781@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=juhl@eisenstein.dk \
--cc=linux-ia64@linuxia64.org \
--cc=linux-kernel@vger.kernel.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