Rajeev Kumar 0fad1762fe qcacld-3.0: Do not log current->comm from hw/sw irq context ... Interrupt handlers do not have valid process context and hence current pointer is not valid for software/hardware interrupt handlers. In WLAN log to user space API current process name is logged using current->comm but hardware/software interrupts do not have corresponding current pointer because they use current pointer of interrupted process. Make changes to not to log process name when log message is generated from hardware/software interrupt handlers. Change-Id: I42420c501f9e7161112c5210909f83755ba4813e CRs-Fixed: 1065898		2016-09-14 15:53:03 -07:00
..
epping	qcacld-3.0: Fix NULL pointer dereferencing issues	2016-09-10 19:08:39 -07:00
fwlog	qcacld-3.0: Fix to resolve checkpatch errors	2016-08-13 14:07:28 -07:00
host_diag_log	qcacld-3.0: Add diag events for debugging	2016-09-10 19:06:23 -07:00
logging	qcacld-3.0: Do not log current->comm from hw/sw irq context	2016-09-14 15:53:03 -07:00
nlink	qcacld-3.0: maintain the backward compatibility for svc events	2016-09-11 17:12:23 -07:00
pktlog	qcacld-3.0: Store events in pktlog buffer when Pktlog is enabled by default in INI	2016-09-10 19:08:41 -07:00
ptt	qcacld-3.0: Logging level changes on wlan HOST	2016-09-10 19:06:06 -07:00