On 5/4/06, Pekka Enberg <[email protected]> wrote:
On 5/4/06, Phillip Hellewell <[email protected]> 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 <[email protected]>
Software-Engineer, IBM LTC Security
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
