Searched refs:libcfs_debug_msg (Results 1 - 7 of 7) sorted by relevance

/drivers/staging/lustre/include/linux/libcfs/linux/
H A Dlibcfs.h109 libcfs_debug_msg(msgdata, \
/drivers/staging/lustre/lustre/libcfs/linux/
H A Dlinux-debug.c154 libcfs_debug_msg(msgdata, "LBUG\n");
/drivers/staging/lustre/include/linux/libcfs/
H A Dlibcfs_debug.h218 libcfs_debug_msg(&msgdata, format, ## __VA_ARGS__); \
257 int libcfs_debug_msg(struct libcfs_debug_msg_data *msgdata,
H A Dlibcfs_private.h64 libcfs_debug_msg(&__msg_data, \
/drivers/staging/lustre/lustre/libcfs/
H A Ddebug.c467 libcfs_debug_msg(msgdata, "Process leaving via %s (rc=%lu : %ld : %#lx)\n",
H A Dtracefile.c246 int libcfs_debug_msg(struct libcfs_debug_msg_data *msgdata, function
258 EXPORT_SYMBOL(libcfs_debug_msg); variable
/drivers/staging/lustre/lustre/obdclass/
H A Dlu_object.c395 * into libcfs_debug_msg-based log. The problem is that lu_object_print()
398 * very well into libcfs_debug_msg() interface that assumes that each message
438 * Printer function emitting messages through libcfs_debug_msg().
463 libcfs_debug_msg(msgdata, "%s", key->lck_area);

Completed in 136 milliseconds