Exactly right. The worst cases are: 1) developers assign messages
to a completely wrong subsystem or 2) don't assign the printk to any
subsystem, in which case we're in exactly the same situation as we are
> It should, however, be an open set, not a closed set like in syslog.
I agree. I'll try to make it as easy as possible to add another
I'm going to work on the sysctl interface for this next.
-- Wild Open Source Inc. firstname.lastname@example.org - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/