From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] [PATCH maint 2/3] batman-adv: Remove unnecessary braces for test_bit() in NC
Date: Fri, 14 Aug 2015 17:23:49 +0200 [thread overview]
Message-ID: <1439565830-9776-2-git-send-email-linus.luessing@c0d3.blue> (raw)
In-Reply-To: <1439565830-9776-1-git-send-email-linus.luessing@c0d3.blue>
Fixes: dfb27e75 ("batman-adv: Fix broken NC capability check")
Signed-off-by: Linus Lüssing <linus.luessing@c0d3.blue>
---
net/batman-adv/network-coding.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/batman-adv/network-coding.c b/net/batman-adv/network-coding.c
index 55a0b28..1a1f7e6 100644
--- a/net/batman-adv/network-coding.c
+++ b/net/batman-adv/network-coding.c
@@ -894,7 +894,7 @@ void batadv_nc_update_nc_node(struct batadv_priv *bat_priv,
goto out;
/* check if orig node is network coding enabled */
- if (!(test_bit(BATADV_ORIG_CAPA_HAS_NC, &orig_node->capabilities)))
+ if (!test_bit(BATADV_ORIG_CAPA_HAS_NC, &orig_node->capabilities))
goto out;
/* accept ogms from 'good' neighbors and single hop neighbors */
--
1.7.10.4
next prev parent reply other threads:[~2015-08-14 15:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 15:23 [B.A.T.M.A.N.] [PATCH maint 1/3] batman-adv: Remove unnecessary braces for test_bit() in DAT Linus Lüssing
2015-08-14 15:23 ` Linus Lüssing [this message]
2015-09-06 8:07 ` [B.A.T.M.A.N.] [PATCH maint 2/3] batman-adv: Remove unnecessary braces for test_bit() in NC Marek Lindner
2015-08-14 15:23 ` [B.A.T.M.A.N.] [PATCH maint 3/3] batman-adv: Remove unnecessary braces for test_bit() in MCAST Linus Lüssing
2015-09-06 8:08 ` Marek Lindner
2015-09-06 8:06 ` [B.A.T.M.A.N.] [PATCH maint 1/3] batman-adv: Remove unnecessary braces for test_bit() in DAT 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=1439565830-9776-2-git-send-email-linus.luessing@c0d3.blue \
--to=linus.luessing@c0d3.blue \
--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).