On 5/4/06, Pekka Enberg <penberg@xxxxxxxxxxxxxx> wrote:
On 5/4/06, Phillip Hellewell <phillip@xxxxxxxxxxxxxxxxxxxx> wrote: > + > +#define ecryptfs_printk(type, fmt, arg...) \ > + __ecryptfs_printk(type "%s: " fmt, __FUNCTION__, ## arg); > +void __ecryptfs_printk(const char *fmt, ...); Why not plain printk?
Originally, ecryptfs_printk was using a verbosity level, which is why there was a custom call wrapping printk. This is no longer the case, and the eCryptfs developers are currently looking at this, and are planning to remove the bulk of printks. Thanks, Mike -- Michael C. Thompson <mcthomps@xxxxxxxxxx> Software-Engineer, IBM LTC Security - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
