summaryrefslogtreecommitdiff
path: root/drivers/usb/musb/musb_host.c
diff options
context:
space:
mode:
authorVivek Goyal <vgoyal@redhat.com>2012-07-18 17:18:12 (GMT)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2012-07-20 00:14:18 (GMT)
commit6791457a090d9a234a40b501c2536f0aefaeae4b (patch)
tree39ba0f7e11dca9a88a38f85ca94b26f46f76365e /drivers/usb/musb/musb_host.c
parentbd8a4f06d0310326f89fd58fed74f2db8e345056 (diff)
downloadlinux-fsl-qoriq-6791457a090d9a234a40b501c2536f0aefaeae4b.tar.xz
printk: Export struct log size and member offsets through vmcoreinfo
There are tools like makedumpfile and vmcore-dmesg which can extract kernel log buffer from vmcore. Since we introduced structured logging, that functionality is broken. Now user space tools need to know about "struct log" and offsets of various fields to be able to parse struct log data and extract text message or dictonary. This patch exports some of the fields. Currently I am not exporting log "level" info as that is a bitfield and offsetof() bitfields can't be calculated. But if people start asking for log level info in the output then we probably either need to seprate out "level" or use bit shift operations for flags and level. Signed-off-by: Vivek Goyal <vgoyal@redhat.com> Acked-by: Kay Sievers <kay@vrfy.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/usb/musb/musb_host.c')
0 files changed, 0 insertions, 0 deletions