Pavel Machek wrote:
>>
>>While we're talking about printk()... is there any reason *not* to
>>rename it printf()?
>
> I believe printf() is good idea. I put printk() into userland programs
> too many times now, and used printf() too many times from kernel.
>
The only reason I can think of *not* to call it printf() is that you may
want to do something for userspace testing like:
#define printk(X, Y...) fprintf(stderr, X, ## Y)
-hpa
-
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 : Sat Dec 07 2002 - 22:00:24 EST