From: Jeff Garzik <jgarzik@pobox.com>
To: Larry Kessler <kessler@us.ibm.com>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
"Andrew V. Savochkin" <saw@saw.sw.com.sg>,
cgl_discussion mailing list <cgl_discussion@osdl.org>,
evlog mailing list <evlog-developers@lists.sourceforge.net>,
"ipslinux (Keith Mitchell)" <ipslinux@us.ibm.com>,
Linus Torvalds <torvalds@home.transmeta.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Hien Nguyen <hien@us.ibm.com>,
James Keniston <kenistoj@us.ibm.com>,
Mike Sullivan <sullivam@us.ibm.com>
Subject: Re: [PATCH-RFC} 3 of 4 - New problem logging macros, plus template generation
Date: Mon, 23 Sep 2002 22:12:02 -0400 [thread overview]
Message-ID: <3D8FC9F2.1020604@pobox.com> (raw)
In-Reply-To: 3D8FC5C8.ED4D4C8@us.ibm.com
> +/*
> + * introduce(), problem(), and detail() macros
> + * Sample usage:
> + * problem(LOG_ALERT, "Disk on fire!",
> + * detail(disk, "%s", drive->name),
> + * detail(temperature, "%d", drive->degC),
> + * detail(action, "%s", "Put out fire; run fsck."));
> + */
action is policy, it does not belong in the kernel at all. Further, I
not sure we need to add all this new infrastructure when we could obtain
the same result via [off the top of my head] printk standards in key
drivers.
Why don't you start out with a list of requirements that you want to see
from drivers? Only then can we objectively evaluate our needs.
You are proposing a solution without really making it clear what
problems you are solving.
Jeff
next prev parent reply other threads:[~2002-09-24 2:07 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-24 1:54 [PATCH-RFC} 3 of 4 - New problem logging macros, plus template generation Larry Kessler
2002-09-24 2:12 ` Jeff Garzik [this message]
2002-09-24 5:47 ` Rusty Russell
2002-09-24 6:05 ` Jeff Garzik
2002-09-24 7:06 ` Rusty Russell
2002-09-24 7:23 ` Jeff Garzik
2002-09-24 7:30 ` Rusty Russell
2002-09-24 19:48 ` alternate event logging proposal Jeff Garzik
2002-09-24 19:57 ` Chris Friesen
2002-09-24 20:03 ` Jeff Garzik
2002-09-24 20:54 ` Tim Hockin
2002-09-24 22:32 ` Brad Hards
2002-09-24 23:31 ` Jeff Garzik
2002-09-24 23:37 ` Brad Hards
2002-09-24 23:59 ` Tim Hockin
2002-09-24 23:38 ` Tim Hockin
2002-09-25 0:09 ` Ben Greear
2002-09-25 0:47 ` Tim Hockin
2002-09-25 1:14 ` Brad Hards
2002-09-25 1:38 ` Tim Hockin
2002-09-24 20:09 ` Jeff Garzik
2002-09-24 20:27 ` [evlog-dev] " Larry Kessler
2002-09-24 20:35 ` Jeff Garzik
2002-09-24 21:11 ` Larry Kessler
2002-09-24 21:26 ` Jeff Garzik
2002-09-25 0:15 ` Larry Kessler
2002-09-24 21:27 ` Horst von Brand
2002-09-24 21:50 ` Larry Kessler
2002-09-25 14:44 ` Lars Marowsky-Bree
2002-09-24 20:54 ` [evlog-dev] " Daniel E. F. Stekloff
2002-09-24 21:04 ` Jeff Garzik
2002-09-30 22:43 ` Pavel Machek
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=3D8FC9F2.1020604@pobox.com \
--to=jgarzik@pobox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cgl_discussion@osdl.org \
--cc=evlog-developers@lists.sourceforge.net \
--cc=hien@us.ibm.com \
--cc=ipslinux@us.ibm.com \
--cc=kenistoj@us.ibm.com \
--cc=kessler@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=saw@saw.sw.com.sg \
--cc=sullivam@us.ibm.com \
--cc=torvalds@home.transmeta.com \
/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