Messages in this thread | | | Date | Thu, 4 May 2006 10:08:03 -0500 | From | "Michael Thompson" <> | Subject | Re: [PATCH 5/13: eCryptfs] Header declarations |
| |
On 5/4/06, Pekka Enberg <penberg@cs.helsinki.fi> wrote: > On 5/4/06, Phillip Hellewell <phillip@hellewell.homeip.net> 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@us.ibm.com> Software-Engineer, IBM LTC Security - 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/
| |