From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] [PATCHv14 0/4] Multicast optimizations for bridges
Date: Tue, 10 May 2016 02:16:01 +0200 [thread overview]
Message-ID: <20160510001601.GK5816@otheros> (raw)
In-Reply-To: <20160510000311.GJ5816@otheros>
On Tue, May 10, 2016 at 02:03:11AM +0200, Linus Lüssing wrote:
> On Thu, May 05, 2016 at 11:15:28PM +0200, Sven Eckelmann wrote:
> > On Thursday 05 May 2016 17:07:01 Linus Lüssing wrote:
> > > This patchset can be found in the current linus/multicast-bridge
> > > branch.
> >
> > Please check the attached results of the daily build test scripts.
>
> Thanks Sven!
Two more questions:
I can ignore return type warnings of sparse for the copy & pasted compat
stuff, right?
Can I ignore the namespace checks mentioned in the end of the log?
If not, how are they usually resolved for such external functions?
Regards, Linus
next prev parent reply other threads:[~2016-05-10 0:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 16:07 [B.A.T.M.A.N.] [PATCHv14 0/4] Multicast optimizations for bridges Linus Lüssing
2016-05-05 16:07 ` [B.A.T.M.A.N.] [PATCHv14 1/4] batman-adv: Always flood IGMP/MLD reports Linus Lüssing
2016-05-08 13:50 ` Marek Lindner
2016-05-05 16:07 ` [B.A.T.M.A.N.] [PATCHv14 2/4] batman-adv: Add multicast optimization support for bridged setups Linus Lüssing
2016-05-05 16:07 ` [B.A.T.M.A.N.] [PATCHv14 3/4] batman-adv: Adding logging of mcast flag changes Linus Lüssing
2016-05-05 17:38 ` Marek Lindner
2016-05-05 16:07 ` [B.A.T.M.A.N.] [PATCHv14 4/4] batman-adv: Add debugfs table for mcast flags Linus Lüssing
2016-05-05 17:38 ` Marek Lindner
2016-05-05 21:15 ` [B.A.T.M.A.N.] [PATCHv14 0/4] Multicast optimizations for bridges Sven Eckelmann
2016-05-10 0:03 ` Linus Lüssing
2016-05-10 0:16 ` Linus Lüssing [this message]
2016-05-10 0:30 ` Linus Lüssing
2016-05-10 7:43 ` Sven Eckelmann
2016-05-10 9:11 ` 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=20160510001601.GK5816@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 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.