Hi Alex,
On 09/19/2014 02:36 PM, Alexander Aring wrote:
Hi Varka,
nice to read you again. :-) I already thought that I was maybe a little
bit too harsh to you for explaining changing dev->add_len during runtime
will occur in unexcept behaviour. Sorry.
For dev->addr_len, i think David asked a question.. Isn't it..?
We need to find a way to add this. Based on this only RFC6775 is going
to work.
But i implemented RFC6775 it works for Extended addresses only. I used
the system
witch use extended address.
Nevertheless welcome back. I want to apply it when Alan finally sends a
"Acked-by: ...", but why is this tagged with bluetooth-next?
I am also waiting for Alan "Acked-by:..." :-)
There are other mrf24j40 patches around and it's better to send this in
a whole patch series when all patches are on wpan-next/testing. Then I
will send these patches to bluetooth-next. When applied I will rebase
the wpan-next/master to bluetooth-next/master.
Ok. I got your point. Thanks... I will respin this series with wpan-next
tag...
Only 6LOWPAN GENERIC patches should be send to bluetooth-next.
Ok.
We are having multiple branches on wpan-next tree.
I want to know which branch is for what,..?
wpan-next/alex/wip
wpan-next/for-martin
wpan-next/for-michael
wpan-next/master
wpan-next/nhc_layer
wpan-next/tcheneau
wpan-next/testing
wpan-next/wpan_rework_rfc
--
Thanks and Regards,
Varka Bhadram.
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
