> +/*
> + * 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Sep 23 2002 - 22:00:41 EST