From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: vda@port.imtp.ilyichevsk.odessa.ua
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KERN_INFO for devfs
Date: Mon, 28 Jan 2002 09:44:45 -0700 [thread overview]
Message-ID: <200201281644.g0SGij202269@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <200201280750.g0S7oGE21742@Port.imtp.ilyichevsk.odessa.ua>
In-Reply-To: <200201280750.g0S7oGE21742@Port.imtp.ilyichevsk.odessa.ua>
Denis Vlasenko writes:
> Primary purpose of this patch is to make KERN_WARNING and
> KERN_INFO log levels closer to their original meaning.
> Today they are quite far from what was intended.
> Just look what kernel writes at the WARNING level
> each time you boot your box!
>
> Diff for devfs.
> --
> vda
>
> diff --recursive -u linux-2.4.13-orig/fs/devfs/base.c linux-2.4.13-new/fs/devfs/base.c
This patch won't even remotely apply to 2.4.18-pre7. Please don't
submit patches which were generated against old kernels unless you've
verified that they apply to the latest kernel.
Furthermore, if you look at 2.4.18-pre7, you'll notice that devfs has
changed the way most of it's messages are generated, and uses the
KERN_ values quite a bit.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
next prev parent reply other threads:[~2002-01-28 16:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-28 11:50 Denis Vlasenko
2002-01-28 16:44 ` Richard Gooch [this message]
2002-01-29 1:20 ` Denis Vlasenko
2002-01-29 16:49 ` Horst von Brand
2002-01-30 13:03 ` Denis Vlasenko
2002-01-30 11:09 ` David Weinehall
2002-01-30 16:32 ` Denis Vlasenko
2002-01-30 12:34 ` Zwane Mwaikambo
2002-01-30 15:16 ` Alan Cox
2002-01-30 18:04 ` Richard Gooch
2002-01-30 18:20 ` Richard Gooch
2002-01-30 18:32 ` Alan Cox
2002-01-30 19:37 ` Jeff Garzik
2002-01-31 20:44 ` Horst von Brand
2002-01-29 7:27 Borsenkow Andrej
2002-01-29 13:40 ` Denis Vlasenko
2002-01-29 10:39 ` Borsenkow Andrej
2002-01-29 15:40 ` Denis Vlasenko
2002-01-29 17:48 ` Richard Gooch
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=200201281644.g0SGij202269@vindaloo.ras.ucalgary.ca \
--to=rgooch@ras.ucalgary.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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
all inboxes | Powered by JetHome®