Commit 011684bd authored by Paul Sokolovsky's avatar Paul Sokolovsky

zephyr/modusocket: Use DEBUG_PRINT macro name as other modules do.

Indeed, just "DEBUG" is too generic.
parent 22fdb915
...@@ -38,8 +38,8 @@ ...@@ -38,8 +38,8 @@
#include <net/net_pkt.h> #include <net/net_pkt.h>
#include <net/dns_resolve.h> #include <net/dns_resolve.h>
#define DEBUG 0 #define DEBUG_PRINT 0
#if DEBUG // print debugging info #if DEBUG_PRINT // print debugging info
#define DEBUG_printf printf #define DEBUG_printf printf
#else // don't print debugging info #else // don't print debugging info
#define DEBUG_printf(...) (void)0 #define DEBUG_printf(...) (void)0
...@@ -165,7 +165,7 @@ static void sock_received_cb(struct net_context *context, struct net_pkt *pkt, i ...@@ -165,7 +165,7 @@ static void sock_received_cb(struct net_context *context, struct net_pkt *pkt, i
DEBUG_printf(" (appdatalen=%d), token: %p", pkt->appdatalen, net_pkt_token(pkt)); DEBUG_printf(" (appdatalen=%d), token: %p", pkt->appdatalen, net_pkt_token(pkt));
} }
DEBUG_printf("\n"); DEBUG_printf("\n");
#if DEBUG > 1 #if DEBUG_PRINT > 1
net_pkt_print_frags(pkt); net_pkt_print_frags(pkt);
#endif #endif
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment