public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: contact <contact@wifibot.com>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] no able to switch routing algo to V ?
Date: Sat, 7 May 2016 20:09:22 +0200	[thread overview]
Message-ID: <572E2F52.6080908@wifibot.com> (raw)
In-Reply-To: <572E2088.7070802@wifibot.com>

I flashed 3 nodes (2 fixe and 1 mobile streaming 2mbits of video data) 
,no crash for the moment.

I am making some test to see if all is ok.

Laurent

On 07/05/2016 19:06, contact wrote:
> seems ok , I will give a try
> (I came today at work only to do some mesh testing on moving robots 
> :-) , never have the time during the week ...)
>
> user@ubuntuvm:~/openwrt15011/openwrt$ git -C feeds/routing log
> commit a3cd8a1729779b8a39336a863ba7f97481e81f5c
> Author: Marek Lindner <mareklindner@neomailbox.ch>
> Date:   Sat May 7 20:42:44 2016 +0800
>
>     batman-adv: 2016.1 bugfixes & stability updates
>
>     Signed-off-by: Marek Lindner <mareklindner@neomailbox.ch>
>
> commit 16ceff232dc58aad799bbb3d98915eb5c78ec2af
> Author: Axel Neumann <neumann@cgws.de>
> Date:   Fri May 6 10:35:47 2016 +0200
>
>     bmx7: bump version (report channel via topology plugin)
>
>
> On 07/05/2016 19:01, Marek Lindner wrote:
>> On Saturday, May 07, 2016 18:59:14 contact wrote:
>>> I just updated I need to recompile and re-flash my nodes it takes
>>> sometime, can you check please if all your patches are here ?
>>>
>>> [..]
>>>
>>> Fast-forward
>>>    ...make-sure-ELP-OGM-orig-MAC-is-updated-on-.patch |  64 
>>> ++++++++++++
>>>    ...-adv-Avoid-duplicate-neigh_node-additions.patch |  89 
>>> +++++++++++++++++
>>> ...Avoid-nullptr-derefence-in-batadv_v_neigh.patch |  38 +++++++
>>> ...an-adv-Fix-refcnt-leak-in-batadv_v_neigh_.patch |  81 
>>> +++++++++++++++
>>> ...Fix-double-neigh_node_put-in-batadv_v_ogm.patch |  40 ++++++++
>>> ...initialize-ELP-orig-address-on-secondary-.patch | 110
>>> +++++++++++++++++++++
>> Looks good. However, comparing git revisions (as Sven suggested) is more
>> precise than posting such logs.
>>
>> Cheers,
>> Marek
>
>


  reply	other threads:[~2016-05-07 18:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-07 14:08 [B.A.T.M.A.N.] no able to switch routing algo to V ? contact
2016-05-07 14:18 ` Sven Eckelmann
2016-05-07 16:04   ` contact
2016-05-07 16:28     ` Sven Eckelmann
2016-05-07 16:42       ` contact
2016-05-07 16:44         ` Sven Eckelmann
2016-05-07 16:51           ` contact
2016-05-07 16:53             ` Marek Lindner
2016-05-07 16:59               ` contact
2016-05-07 17:01                 ` Marek Lindner
2016-05-07 17:06                   ` contact
2016-05-07 18:09                     ` contact [this message]
2016-05-07 18:45                       ` contact
2016-05-07 22:40                         ` Marek Lindner
2016-05-07 16:55             ` Sven Eckelmann
  -- strict thread matches above, loose matches on Subject: below --
2016-05-06 20:27 [B.A.T.M.A.N.] [PATCH maint] batman-adv: Fix double neigh_node_put in batadv_v_ogm_route_update Sven Eckelmann
2016-05-07 12:07 ` Marek Lindner
2016-05-07 12:29   ` [B.A.T.M.A.N.] no able to switch routing algo to V ? contact
2016-05-07 13:14     ` 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=572E2F52.6080908@wifibot.com \
    --to=contact@wifibot.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