This is qcacld-2.0 to qcacld-3.0 propagation Avoid logging of all module logs into kmsg during the driver load phase. All module log level is set much before setting of the flag that indicates whether multicast logging is enabled or not. Because of this all module log levels are getting printed for a brief duration in kmsg during driver load. Fix the same by setting the multicast flag appropriately so that when multicast logging is enabled, all the logs are multicast to user space and only the error and fatal messages continue to get logged in the kmsg. CRs-Fixed: 958705 Change-Id: I260e38ef64f704dfd9ca1ca4dc68c56428526559 |
||
---|---|---|
.. | ||
bmi | ||
cdf | ||
cds | ||
dp | ||
hdd | ||
hif | ||
htc | ||
mac | ||
sap | ||
sme | ||
utils | ||
wma | ||
wmi |