From: James Tucker <jftucker@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: [PATCH] ipc: fix code style
Date: Mon, 9 Jan 2017 19:49:34 -0800 [thread overview]
Message-ID: <20170110034934.40836-1-jftucker@gmail.com> (raw)
best we don't goto fail by accident.
---
src/tools/ipc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/tools/ipc.c b/src/tools/ipc.c
index 6237961..0e90b3c 100644
--- a/src/tools/ipc.c
+++ b/src/tools/ipc.c
@@ -240,7 +240,7 @@ static int userspace_get_device(struct wgdevice **dev, const char *interface)
if ((uint8_t *)peer + sizeof(struct wgpeer) > (uint8_t *)*dev + len)
goto out;
if ((uint8_t *)peer + sizeof(struct wgpeer) + sizeof(struct wgipmask) * peer->num_ipmasks > (uint8_t *)*dev + len)
- goto out;
+ goto out;
}
ret = 0;
out:
--
2.11.0
reply other threads:[~2017-01-10 3:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170110034934.40836-1-jftucker@gmail.com \
--to=jftucker@gmail.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).