danielfsantos@xxxxxxx wrote: > Typically, we don't care about error messages or names in the kernel because > userspace will manage that. But sometimes we need to output an error number > to printks and that creates a situation where a user, system admistrator or > developer must find an error number reference to figure out what went wrong > with a particular driver or whatever. This patch adds two alternatives at > increasing memory costs: > > 1. print the number in addition to the name for 2k extra or > 2. print the number, name and description for 6k extra. I like the idea generally - and have occasionally entertained the idea of implementing it myself. However, I wouldn't bother with the "human readable" description if we're going to do this. Generally, the symbolic representation is good enough - and that's what you're going to grep the code for anyway. David -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
