From: Alexander Aring <alex.aring@gmail.com>
To: Jukka Rissanen <jukka.rissanen@linux.intel.com>
Cc: linux-wpan@vger.kernel.org, kernel@pengutronix.de,
linux-bluetooth@vger.kernel.org
Subject: Re: [RFCv2 bluetooth-next 0/2] 6lowpan: introduce generic 6lowpan private data
Date: Mon, 3 Aug 2015 15:39:17 +0200 [thread overview]
Message-ID: <20150803133913.GA30530@omega> (raw)
In-Reply-To: <1438590118.2896.224.camel@linux.intel.com>
On Mon, Aug 03, 2015 at 11:21:58AM +0300, Jukka Rissanen wrote:
> Hi Alex,
>
> On pe, 2015-07-31 at 14:38 +0200, Alexander Aring wrote:
> > Hi,
> >
> > I already thought many times to introduce something like that. Here is a draft
> > for introducing the generic 6lowpan private data into each lowpan interface.
> > For the beginning I introduced the enum "ll_type" which contains the LL type of
> > a lowpan interface.
>
> Acked-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
>
>
> BTW, did you document the description below somewhere, it looks very
> useful.
>
no, maybe we can create a "Documentation/networking/6lowpan.txt" for
this?
- Alex
next prev parent reply other threads:[~2015-08-03 13:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 12:38 [RFCv2 bluetooth-next 0/2] 6lowpan: introduce generic 6lowpan private data Alexander Aring
2015-07-31 12:38 ` [RFCv2 bluetooth-next 1/2] bluetooth: 6lowpan: change netdev_priv to lowpan_dev Alexander Aring
2015-08-04 13:11 ` Stefan Schmidt
2015-07-31 12:38 ` [RFCv2 bluetooth-next 2/2] 6lowpan: add generic 6lowpan netdev private data Alexander Aring
2015-08-04 13:11 ` Stefan Schmidt
2015-08-03 8:21 ` [RFCv2 bluetooth-next 0/2] 6lowpan: introduce generic 6lowpan " Jukka Rissanen
2015-08-03 13:39 ` Alexander Aring [this message]
2015-08-03 13:54 ` Jukka Rissanen
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=20150803133913.GA30530@omega \
--to=alex.aring@gmail.com \
--cc=jukka.rissanen@linux.intel.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