public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
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.] Batman-adv 2014.1.0 and 2014.0.0 issues with 3.10 and 3.8 kernels
Date: Wed, 02 Apr 2014 01:11:38 +0800	[thread overview]
Message-ID: <1710557.rN7xxoT97v@diderot> (raw)
In-Reply-To: <6EA59799-2CB9-4B60-83A9-C0F1893B70B1@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 868 bytes --]

On Tuesday 01 April 2014 11:01:16 Bruno Antunes wrote:
> > This is a known 2014.1.0 regression which recently has been fixed. You can
> > either update your openwrt package to fetch these fixes or extract the
> > patches from our batman-adv git repository or wait for the next release.
> 
> Compiled with the latest update (31 Mar) and up until now it's working fine
> on both devices.

Great!


> > Note that this is not the official openwrt-routing repository but a fork
> > maintained by 'people on the internet'. If you do experience problems with
> > the code coming from this repository, please contact the people
> > maintaining this fork.
> 
> Didn't found any problems with this fork.

I did not mean to imply using some other repository is necessarily a bad 
thing. Just keep in mind to bother the right people _in case_ something goes 
awry.

Cheers,
Marek

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

      reply	other threads:[~2014-04-01 17:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-31 11:23 [B.A.T.M.A.N.] Batman-adv 2014.1.0 and 2014.0.0 issues with 3.10 and 3.8 kernels Bruno Antunes
2014-03-31 13:02 ` Marek Lindner
2014-04-01  0:25   ` cmsv
2014-04-01  2:54     ` Gui Iribarren
2014-04-01 11:16       ` Bastian Bittorf
2014-04-01 10:01   ` Bruno Antunes
2014-04-01 17:11     ` 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=1710557.rN7xxoT97v@diderot \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox