From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: "Linus Lüssing" <linus.luessing@c0d3.blue>,
"Linus Lüssing" <linus.luessing@c0d3.blue>
Subject: Re: [PATCH maint v3 3/3] batman-adv: mcast: fix duplicate mcast packets from BLA backbone to mesh
Date: Mon, 14 Sep 2020 21:12:00 +0200 [thread overview]
Message-ID: <6205936.0nzyDX8fZS@sven-edge> (raw)
In-Reply-To: <20200914012136.5278-4-linus.luessing@c0d3.blue>
[-- Attachment #1: Type: text/plain, Size: 521 bytes --]
On Monday, 14 September 2020 03:21:36 CEST Linus Lüssing wrote:
> + * Check if it is on our broadcast list. Another gateway might have sent the
> + * same packet because it is connected to the same backbone, so we have to
> + * remove this duplicate.
> +
> * This is performed by checking the CRC, which will tell us
There is a "*" missing in the last added kerneldoc line. This causes following
warning message:
./net/batman-adv/bridge_loop_avoidance.c:1594: warning: bad line:
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-09-14 19:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 1:21 [PATCH maint v3 0/3] batman-adv: mcast: BLA fixes Linus Lüssing
2020-09-14 1:21 ` [PATCH maint v3 1/3] batman-adv: mcast: fix duplicate mcast packets in BLA backbone from LAN Linus Lüssing
2020-09-14 18:12 ` Sven Eckelmann
2020-09-14 1:21 ` [PATCH maint v3 2/3] batman-adv: mcast: fix duplicate mcast packets in BLA backbone from mesh Linus Lüssing
2020-09-14 1:21 ` [PATCH maint v3 3/3] batman-adv: mcast: fix duplicate mcast packets from BLA backbone to mesh Linus Lüssing
2020-09-14 19:12 ` Sven Eckelmann [this message]
2020-09-14 18:31 ` [PATCH maint v3 0/3] batman-adv: mcast: BLA fixes Sven Eckelmann
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=6205936.0nzyDX8fZS@sven-edge \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=linus.luessing@c0d3.blue \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.