From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] [PATCH] batman-adv: else should follow close brace '}'
Date: Mon, 14 Feb 2011 10:10:23 +0100 [thread overview]
Message-ID: <1297674623-3130-1-git-send-email-sven@narfation.org> (raw)
Signed-off-by: Sven Eckelmann <sven@narfation.org>
---
batman-adv/gateway_client.c | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/batman-adv/gateway_client.c b/batman-adv/gateway_client.c
index 3486854..41eba8a 100644
--- a/batman-adv/gateway_client.c
+++ b/batman-adv/gateway_client.c
@@ -123,8 +123,7 @@ void gw_election(struct bat_priv *bat_priv)
"Removing selected gateway - "
"no gateway in range\n");
gw_deselect(bat_priv);
- }
- else
+ } else
rcu_read_unlock();
return;
--
1.7.2.3
next reply other threads:[~2011-02-14 9:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 9:10 Sven Eckelmann [this message]
2011-02-14 12:57 ` [B.A.T.M.A.N.] [PATCH] batman-adv: else should follow close brace '}' Marek Lindner
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=1297674623-3130-1-git-send-email-sven@narfation.org \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/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).