[lkml]   [2002]   [Sep]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH-RFC} 3 of 4 - New problem logging macros, plus template generation
In message <> 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.

Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:29    [W:0.072 / U:3.016 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site