From: Marek Lindner <lindner_marek@yahoo.de>
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.] bridge loop avoidance (v3)
Date: Sat, 9 Oct 2010 13:41:07 +0200 [thread overview]
Message-ID: <201010091341.08096.lindner_marek@yahoo.de> (raw)
In-Reply-To: <201009291520.13588.lindner_marek@yahoo.de>
On Wednesday 29 September 2010 15:20:13 Marek Lindner wrote:
> the received comments motivated me to reword the commit messages to outline
> that the loop is caused by bridging the payload traffic and not by the LAN
> itself. Furthermore, the locking has been cleaned up and the neighbor list
> is purged when the module is unloaded.
Since no more new questions came up I merged the patches into trunk (revision
1816-1817).
Regards,
Marek
prev parent reply other threads:[~2010-10-09 11:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 13:20 [B.A.T.M.A.N.] bridge loop avoidance (v3) Marek Lindner
2010-09-29 13:20 ` [B.A.T.M.A.N.] [PATCHv3 1/2] batman-adv: softif bridge loop avoidance Marek Lindner
2010-09-29 13:20 ` [B.A.T.M.A.N.] [PATCHv3 2/2] batctl: display soft-interface neighbor table Marek Lindner
2010-10-09 11:41 ` Marek Lindner [this message]
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=201010091341.08096.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--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