From: Rusty Russell <rusty@rustcorp.com.au>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
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>,
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: Tue, 24 Sep 2002 17:06:27 +1000 [thread overview]
Message-ID: <20020924070706.D3A332C189@lists.samba.org> (raw)
In-Reply-To: Your message of "Tue, 24 Sep 2002 02:05:45 -0400." <3D9000B9.4000001@pobox.com>
In message <3D9000B9.4000001@pobox.com> you write:
> The backend is fairly sound. And I agree in general event logging is
> useful, and I fully support integrating [sane] support into the kernel.
>
> But the kernel API is utter crap.
>
> Adding <foo>_problem.h for every subsystem?
<sigh>. That's an extension, designed to make things *easier* on the
author, for example to share code between network drivers. But I'm
more than happy to grow them on demand (you know IBM programmers,
they're always want "completeness").
> Changing every printk() in the damn kernel?
>
> Come on dude, I _know_ you have more taste than that.
I'm not interested in changing all the printks. I'm interested in
designing the simplest regularized logging interface I can. If it's
done right, driver authors will migrate to it because it's easier for
them, and their bug reports become clearer, and sysadmins get happier.
And even though they don't care about the eventlogging tools, all that
stuff becomes exponentially more useful as a bonus.
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2002-09-24 7:01 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
2002-09-24 5:47 ` Rusty Russell
2002-09-24 6:05 ` Jeff Garzik
2002-09-24 7:06 ` Rusty Russell [this message]
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=20020924070706.D3A332C189@lists.samba.org \
--to=rusty@rustcorp.com.au \
--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=jgarzik@pobox.com \
--cc=kenistoj@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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