From 7e3cf5f461eb4fbb7581672bf0835da07c378136 Mon Sep 17 00:00:00 2001 From: Christian Grothoff Date: Thu, 31 Oct 2019 13:03:48 +0100 Subject: tighten formatting rules --- src/util/socks.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'src/util/socks.c') diff --git a/src/util/socks.c b/src/util/socks.c index c2e012f1c..756be753a 100644 --- a/src/util/socks.c +++ b/src/util/socks.c @@ -387,8 +387,7 @@ transmit_ready (void *cls, size_t size, void *buf) * connection.c tells us nothing itself, but mostly its timouts. * Initially, we'll simply ignore this and leave massive timeouts, but * maybe that should change for error handling pruposes. It appears that - * successful operations, including DNS resolution, do not use this. */ - if (NULL == buf) + * successful operations, including DNS resolution, do not use this. */if (NULL == buf) { if (0 == ih->step) { @@ -629,7 +628,7 @@ GNUNET_SOCKS_do_connect (const char *service_name, port0 = 9050; /* A typical Tor client should usually try port 9150 for the TBB too, but * GNUnet can probably assume a system Tor installation. */ - if ((port0 > 65535)||(port0 <= 0)) + if ((port0 > 65535) || (port0 <= 0)) { LOG (GNUNET_ERROR_TYPE_WARNING, _ ( @@ -686,4 +685,5 @@ GNUNET_SOCKS_do_connect (const char *service_name, return GNUNET_SOCKS_run_handshake (ih, socks5); } + /* socks.c */ -- cgit v1.2.3