From: "Ph. Marek" <philipp.marek@bmlv.gv.at>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH available] Re: printk() without KERN_ prefixes? (in 2.5.59)
Date: Fri, 24 Jan 2003 12:32:28 +0100 [thread overview]
Message-ID: <200301241232.28151.philipp.marek@bmlv.gv.at> (raw)
In-Reply-To: <12940.1043141000@ocs3.intra.ocs.com.au>
> >Should they be fixed to KERN_INFO or some such? I'm willing to contribute
> > a patch (which will be done by script, of course). Or am I missing
> > something and they shall stay as they are?
>
> Do not blindly add KERN_*. Some prints are done with multiple calls to
> printk(), only the first call should have KERN_*, otherwise you get
> lines like this, with embedded '<n>' strings.
Well, I wrote a perl-script (available on request) which searches for missing
KERN_ values.
It does this by reading filenames from STDIN, reading the files, extracting
every function from there and checking if after \n is a KERN_-value (assuming
that every function starts from a fresh line). If there is one missing,
KERN_DEBUG is inserted.
my simple script was unable to do some files in the arch/ia64 tree and some
others because using #if with mis-aligned { and }. example from
sound/isa/opti9xx/opti92x-ad1848.c
#ifdef __ISAPNP__
if (isapnp && (hw = snd_card_opti9xx_isapnp(chip)) > 0) {
...
} else {
#endif /* __ISAPNP__ */
...
#ifdef __ISAPNP__
}
#endif /* __ISAPNP__ */
and it just doesn't check such constructs.
Furthermore it destroys some files (don't know why atm), but these are
manually excluded from the patch, which is 3933078 bytes (bzipped2 699170).
This patch has NOT all occurances fixed!
from diffstat:
1908 files changed, 13568 insertions(+), 13567 deletions(-)
So I think it not really useful to just post this patch to the list.
I think I'll cut it at subdirectory levels in pieces (ie arch/ia64, arch/i386,
drivers/net, drivers/scsi ...).
I should have them available some time monday for the interested.
Comments?
Regards,
Phil
next prev parent reply other threads:[~2003-01-24 11:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-21 8:58 printk() without KERN_ prefixes? (in 2.5.59) and Q: small kernel image doc Ph. Marek
2003-01-21 9:23 ` Keith Owens
2003-01-24 11:32 ` Ph. Marek [this message]
2003-02-12 15:10 ` [PATCHes] printk() without KERN_ prefixes for 2.5.60 Ph. Marek
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=200301241232.28151.philipp.marek@bmlv.gv.at \
--to=philipp.marek@bmlv.gv.at \
--cc=kaos@ocs.com.au \
--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
all inboxes | Powered by JetHome®