From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCHv13 0/4] Multicast optimizations for bridges
Date: Tue, 19 Apr 2016 04:28:38 +0200 [thread overview]
Message-ID: <20160419022838.GF17647@otheros> (raw)
In-Reply-To: <1461031839-31182-1-git-send-email-linus.luessing@c0d3.blue>
On Tue, Apr 19, 2016 at 04:10:35AM +0200, Linus Lüssing wrote:
> Changes in v13:
> * Substituted a non-breaking space with a boring one
> * Dropped compat code for kernels < 3.2
> * Removed mcast tvlv container and handler support for v1 completely
> * Rebase to current master branch
> (automatic 3-way merge without issues)
The last changes in v13 are just compile and not runtime tested so
far. Hopefully will do this within the next few days. But, ehm,
should be minor anyways (..., which were the last words he mumbled
before stepping on the deadly null pointer :P).
But I thought, it might be a good idea to mail them already in
case Simon wants to do his testing in parallel this weekend :).
Regards, Linus
next prev parent reply other threads:[~2016-04-19 2:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 2:10 [B.A.T.M.A.N.] [PATCHv13 0/4] Multicast optimizations for bridges Linus Lüssing
2016-04-19 2:10 ` [B.A.T.M.A.N.] [PATCHv13 1/4] batman-adv: Always flood IGMP/MLD reports Linus Lüssing
2016-04-19 2:10 ` [B.A.T.M.A.N.] [PATCHv13 2/4] batman-adv: Add multicast optimization support for bridged setups Linus Lüssing
2016-04-19 2:10 ` [B.A.T.M.A.N.] [PATCHv13 3/4] batman-adv: Adding logging of mcast flag changes Linus Lüssing
2016-04-19 2:10 ` [B.A.T.M.A.N.] [PATCHv13 4/4] batman-adv: Add debugfs table for mcast flags Linus Lüssing
2016-04-19 2:28 ` Linus Lüssing [this message]
2016-05-05 15:05 ` [B.A.T.M.A.N.] [PATCHv13 0/4] Multicast optimizations for bridges Simon Wunderlich
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=20160419022838.GF17647@otheros \
--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