From: Marek Lindner <mareklindner@neomailbox.ch>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCHv15 3/4] batman-adv: Adding logging of mcast flag changes
Date: Thu, 12 May 2016 23:21:14 +0800 [thread overview]
Message-ID: <2545852.G7PSWjTTnL@voltaire> (raw)
In-Reply-To: <1462898487-9696-4-git-send-email-linus.luessing@c0d3.blue>
[-- Attachment #1: Type: text/plain, Size: 618 bytes --]
On Tuesday, May 10, 2016 18:41:26 Linus Lüssing wrote:
> With this patch changes relevant to a node's own multicast flags are
> printed to the 'mcast' log level.
>
> Tested-by: Simon Wunderlich <sw@simonwunderlich.de>
> Signed-off-by: Linus Lüssing <linus.luessing@c0d3.blue>
> ---
> net/batman-adv/main.h | 4 +-
> net/batman-adv/multicast.c | 133
> ++++++++++++++++++++++++++++++++++++++- net/batman-adv/soft-interface.c
> | 4 ++
> net/batman-adv/types.h | 4 ++
> 4 files changed, 142 insertions(+), 3 deletions(-)
Applied in revision ffdce4f.
Thanks,
Marek
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-05-12 15:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 16:41 [B.A.T.M.A.N.] [PATCHv15 0/4] Multicast optimizations for bridges Linus Lüssing
2016-05-10 16:41 ` [B.A.T.M.A.N.] [PATCHv15 1/4] batman-adv: Always flood IGMP/MLD reports Linus Lüssing
2016-05-12 15:14 ` Marek Lindner
2016-05-10 16:41 ` [B.A.T.M.A.N.] [PATCHv15 2/4] batman-adv: Add multicast optimization support for bridged setups Linus Lüssing
2016-05-12 15:19 ` Marek Lindner
2016-05-10 16:41 ` [B.A.T.M.A.N.] [PATCHv15 3/4] batman-adv: Adding logging of mcast flag changes Linus Lüssing
2016-05-12 15:21 ` Marek Lindner [this message]
2016-05-10 16:41 ` [B.A.T.M.A.N.] [PATCHv15 4/4] batman-adv: Add debugfs table for mcast flags Linus Lüssing
2016-05-12 15:22 ` Marek Lindner
2016-05-10 16:50 ` [B.A.T.M.A.N.] [PATCHv15 0/4] Multicast optimizations for bridges Linus Lüssing
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=2545852.G7PSWjTTnL@voltaire \
--to=mareklindner@neomailbox.ch \
--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 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.