From: Sven Eckelmann <sven@narfation.org>
To: 张鹏 <1805692831@qq.com>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: 回复： openwrt batman-adv
Date: Sat, 28 Dec 2019 06:40:41 +0100 [thread overview]
Message-ID: <43821815.iu2yF5aFiK@sven-edge> (raw)
In-Reply-To: <tencent_CA5610319E19CB95CA9DB432847536DEFF09@qq.com>
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
On Saturday, 28 December 2019 03:32:17 CET 张鹏 wrote:
> Thank you very much for your reply!
> I have ported the pre-2019.2 version of batman to the 3.3 kernel and it is available for doing
Please don't do this. Now you are not only having the known bugs from Linux
3.3 but also the known bugs [1] from the pre-2019.2 batman-adv.
The correct approach is to get your used software updated to a non-EOL
version.
Kind regards,
Sven
[1] https://git.open-mesh.org/batman-adv.git/blob/HEAD:/CHANGELOG.rst
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-12-28 5:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-24 8:37 openwrt batman-adv =?gb18030?B?1cXF9A==?=
2019-12-24 9:03 ` Sven Eckelmann
[not found] ` <tencent_CA5610319E19CB95CA9DB432847536DEFF09@qq.com>
2019-12-28 5:40 ` Sven Eckelmann [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=43821815.iu2yF5aFiK@sven-edge \
--to=sven@narfation.org \
--cc=1805692831@qq.com \
--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