From: Alexander Aring <alex.aring@gmail.com>
To: Michael C Cambria <mcc@fid4.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: [ANNOUNCE] wpan-tools 0.3 released
Date: Sun, 7 Dec 2014 18:13:13 +0100 [thread overview]
Message-ID: <20141207171311.GB9532@omega> (raw)
In-Reply-To: <548487CF.4060009@fid4.com>
Hi,
please use bluetooth-next [0] for the wpan-tools. For experiment things use
wpan_rework_rfc branch. I have still patches there which should be go
into mainline but isn't easy to touch the code without breaking.
Also for patches please base on bluetooth-next.
On Sun, Dec 07, 2014 at 12:01:03PM -0500, Michael C Cambria wrote:
> On 12/07/14 10:08, Alexander Aring wrote:
> >Hi, I'm happy to announce that I've just released wpan-tools 0.3. This is
> >our first "real" release, the new kernel 3.18 will contain the nl802154
> >interface. The old netlink interface will be removed soon and is
> >deprecated now. At the moment you can still use both userspace tools, but
> >I don't recommend the lowpan-tools. New release will be found now under:
> >http://wpan.cakelab.org/releases/
>
> Should we using https://github.com/linux-wpan/linux-wpan-next or
mhh, better I update this branch now to bluetooth-next since nl802154
seems to be work.
> https://github.com/linux-wpan/linux-wpan-next/tree/wpan_rework_rfc
>
- Alex
[0] http://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-next.git
next prev parent reply other threads:[~2014-12-07 17:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-07 15:08 [ANNOUNCE] wpan-tools 0.3 released Alexander Aring
2014-12-07 17:01 ` Michael C Cambria
2014-12-07 17:13 ` Alexander Aring [this message]
2014-12-07 17:19 ` Alexander Aring
2014-12-07 21:39 ` Michael C Cambria
2014-12-07 21:54 ` Alexander Aring
2014-12-11 15:02 ` Michael C. Cambria
2014-12-11 16:31 ` Alexander Aring
2015-01-06 19:18 ` Maciej Wasilak
2015-01-06 19:44 ` Alexander Aring
2014-12-12 8:54 ` Stefan Schmidt
2014-12-13 8:55 ` Alexander Aring
2014-12-15 8:29 ` Stefan Schmidt
2014-12-15 8:35 ` Alexander Aring
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=20141207171311.GB9532@omega \
--to=alex.aring@gmail.com \
--cc=linux-wpan@vger.kernel.org \
--cc=mcc@fid4.com \
/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