linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Schmidt <stefan@osg.samsung.com>
To: Alexander Aring <aar@pengutronix.de>, linux-wpan@vger.kernel.org
Cc: linux-bluetooth@vger.kernel.org, kernel@pengutronix.de,
	jukka.rissanen@linux.intel.com
Subject: Re: [RFC bluetooth-next] 6lowpan: move reciving handling to generic
Date: Fri, 29 Jan 2016 15:15:45 +0100	[thread overview]
Message-ID: <56AB7411.3000700@osg.samsung.com> (raw)
In-Reply-To: <1453927574-5074-1-git-send-email-aar@pengutronix.de>

Hello.

On 27/01/16 21:46, Alexander Aring wrote:
> This patch moves 6lowpan receive handling into 6lowpan generic. I
> introduced some callback ops to make some link-layer specific handling.
>
> Signed-off-by: Alexander Aring <aar@pengutronix.de>
> ---
> Hi,
>
> this patch is a draft to talking about to move the receive handling
> and evaluation of 6LoWPAN dispatches into net/6lowpan instead that
> every 6lowpan specific link-layer implementation will do that on his
> own.
>
> I added some callbacks for receive handling, other solutions would
> be to add runtime decisions into net/6lowpan/rx.c by eval the
> interface type.
>
> Any comments are welcome. It's not perfect yet and it can be still
> improved at some places, if we really like to go that way.

The first questions that comes to mind is why rx only and not tx?
This would also allow the fragment handling to move into the generic 
part. I'm aware that bluetooth is not using it but other 6LoWPAN 
adaptation layers do and it part of the RFC4944.

regards
Stefan Schmidt

  reply	other threads:[~2016-01-29 14:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27 20:46 [RFC bluetooth-next] 6lowpan: move reciving handling to generic Alexander Aring
2016-01-29 14:15 ` Stefan Schmidt [this message]
2016-02-01 10:10   ` 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=56AB7411.3000700@osg.samsung.com \
    --to=stefan@osg.samsung.com \
    --cc=aar@pengutronix.de \
    --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;
as well as URLs for NNTP newsgroup(s).