From: Jukka Rissanen <jukka.rissanen@linux.intel.com>
To: Alexander Aring <alex.aring@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, linux-wpan@vger.kernel.org,
kernel@pengutronix.de
Subject: Re: creating infrastructure for generic 6LoWPAN branch
Date: Tue, 14 Apr 2015 15:28:06 +0300 [thread overview]
Message-ID: <1429014486.2837.81.camel@linux.intel.com> (raw)
In-Reply-To: <20150414114917.GA2179@omega>
Hi Alex,
On ti, 2015-04-14 at 13:49 +0200, Alexander Aring wrote:
> Hi,
>
> I was thinking about to create some infrastructure to handle generic
> 6LoWPAN development things, which is shared between bluetooth and
> 802.15.4. I mean everything which is in "net/6lowpan" and things which
> are 6LoWPAN "specific/related/mostly used in 6LoWPAN" and works in L3 and
> upper layers.
>
> What we should need is some kind of website which contains a ToDo list
> of everything which is outside there and what we currently support. I
> mean a general information site for "6LoWPAN" implementation inside
> Linux kernel.
>
> Additionally we need some repository which contains some userspace tools
> for handling generic 6LoWPAN things like userspace configuration tool
> for the 6LoWPAN nhc layer. These tools can be used then for all 6LoWPAN
> implementations (BTLE/802.15.4 at the moment). That was one idea which
> was discussed while bringing nhc layer mainline.
>
> Any ideas where we should host this site, do we really need this or
> any others suggestions?
As Marc suggested, the kernel.org wiki would be a good choice. And all
the userspace tools could be there also.
Cheers,
Jukka
prev parent reply other threads:[~2015-04-14 12:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 11:49 creating infrastructure for generic 6LoWPAN branch Alexander Aring
2015-04-14 11:52 ` Marc Kleine-Budde
2015-04-14 12:28 ` Jukka Rissanen [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=1429014486.2837.81.camel@linux.intel.com \
--to=jukka.rissanen@linux.intel.com \
--cc=alex.aring@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wpan@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).