lkml.org 
[lkml]   [2000]   [Jan]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [patch-2.3.40-pre6] kzalloc() (ala kmem_zalloc() of SVR4)
Date
From
In message <Pine.SV4.3.96.1000122113149.17095C-100000@scofolks.ocston.org>, 
Tig
ran Aivazian writes:
+-----
| > Why do we have printk anyway? It serves the same purpose as printf and
| > is even tagged as `taking arguments like printf' for gcc's type-checking
| > benefit.
|
| It is actually subtly different (the <N> priority thing) which I always
| thought was the reason why printk() is not called printf(). It is not
+--->8

printk() predates support for priorities in kernel messages. I vaguely
recall it being related to "don't link libc into the kernel", but don't
quote me on that.

--
brandon s. allbery os/2,linux,solaris,perl allbery@kf8nh.apk.net
system administrator kthkrb,heimdal,gnome,rt allbery@ece.cmu.edu
carnegie mellon / electrical and computer engineering kf8nh
We are Linux. Resistance is an indication that you missed the point.



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:56    [W:0.592 / U:0.484 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site