From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: kessler@us.ibm.com (Larry Kessler)
Cc: linux-kernel@vger.kernel.org (Linux Kernel Mailing List)
Subject: Re: [PATCH-RFC] POSIX Event Logging, kernel 2.5.6 & 2.4.18y
Date: Fri, 15 Mar 2002 01:49:25 +0000 (GMT) [thread overview]
Message-ID: <E16lgqT-0002Vv-00@the-village.bc.nu> (raw)
In-Reply-To: <3C914BC3.2B05C62E@us.ibm.com> from "Larry Kessler" at Mar 14, 2002 05:17:55 PM
> I am absolutely open to suggestions for making printk messages better
> and more useful--we just haven't figured-out how yet.
What you don't want to do is break printk. In AberMUD I used macros for
something similar
#define Module static char *Mod_Name=
#define Version static char *Ver_Name=
#define Author static char *Aut_Name=
#define Error(x) ErrFunc((x),Mod_Name,Ver_Name,__LINE__,__FILE__)
And drivers started
Module "System";
Version "1.28";
Author "----*(A)";
However that doesn't work for varargs. Nevertheless something of a similar
approach might let you avoid breaking printk in most old code. If you can
avoid a grand replacement of printk you win lots of friends. If you can
do it in a way that people can do automated parsing of kernel messages
for translation tables in klogd/initlog/dmesg you also win lots of friends.
next prev parent reply other threads:[~2002-03-15 1:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 1:17 [PATCH-RFC] POSIX Event Logging, kernel 2.5.6 & 2.4.18 Larry Kessler
2002-03-15 1:49 ` Alan Cox [this message]
2002-03-15 2:14 [PATCH-RFC] POSIX Event Logging, kernel 2.5.6 & 2.4.18y Tony.P.Lee
2002-03-15 14:44 ` Alan Cox
2002-03-18 21:48 ` Larry Kessler
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=E16lgqT-0002Vv-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=kessler@us.ibm.com \
--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;
as well as URLs for NNTP newsgroup(s).