commit f9bdd4e2762edf294eaf499207afa4e4d83108a6
author Madan Mohan Koyyalamudi <c_mkoyya@qca.qualcomm.com> Tue Oct 30 18:05:03 2012 -0700
committer Jeff Johnson <jjohnson@qca.qualcomm.com> Fri Nov 30 14:58:55 2012 -0800
tree 46f5009813b67a3474082d5c679e4a98d4c4ccf3
parent 2c112c5c79ffb51d90bce655248253fa7e7ddbaf

wlan: Use unique logging for driver commands

There are two different mechanisms by which driver commands may be sent,
either by Wireless Extensions private ioctls or by regualr device
private ioctls.  Currently when processing a driver command the log
message does not indicate via which mechanism the command was received.
Since knowing this information aids in debugging, modify the log
messages so that they indicated the function that is handling the
message.

Change-Id: I137d4b4d707eece07bf4b4fd5c39a15836af0e9b
CR-Fixed: 414855

CORE/HDD/src/wlan_hdd_main.c

diff --git a/CORE/HDD/src/wlan_hdd_main.c b/CORE/HDD/src/wlan_hdd_main.c
index 709b2b9..a4ba6a7 100644
--- a/CORE/HDD/src/wlan_hdd_main.c
+++ b/CORE/HDD/src/wlan_hdd_main.c
@@ -393,7 +393,7 @@
        hdd_context_t *pHddCtx = (hdd_context_t*)pAdapter->pHddCtx;
 
        VOS_TRACE( VOS_MODULE_ID_HDD, VOS_TRACE_LEVEL_INFO,
-                   "***Received %s cmd from Wi-Fi GUI***", command);
+                  "%s: Received %s cmd from Wi-Fi GUI***", __func__, command);
 
        if (strncmp(command, "P2P_DEV_ADDR", 12) == 0 )
        {
@@ -447,6 +447,11 @@
 
            ret = sapSetPreferredChannel(dev, ptr);
        }
+       else {
+           hddLog( VOS_TRACE_LEVEL_WARN, "%s: Unsupported GUI command %s",
+                   __func__, command);
+       }
+
    }
 exit:
    if (command)