On 09/20/2013 08:07 AM, David Howells wrote:
I suspect he doesn't really need to implement a "strerror()" function but should rather build it straight into printk()/vsprintf(). David
Indeed we don't necessarily *need* a strerror() function per-se, but it is an addition to the libc support in the kernel. I'll leave it up to the community to decide rather or not it should be separate or integrated into vsprintf.c. Also, there is no POSIX or GNU libc extension (that I am aware of) to print an error name -- a real shame imho, so the name strerror_name() is pretty much artificial. Is there a significant overhead in having these functions exported?
Personally, I would think that the only reason to have interest in an error name or message in the kernel is to output via printk, but I like to allow room for the conditions that I may not have thought of.
Daniel -- 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
