From: Alexander Aring <alex.aring@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: kernel@pengutronix.de, Alexander Aring <alex.aring@gmail.com>,
Jukka Rissanen <jukka.rissanen@linux.intel.com>
Subject: [RFC bluetooth-next 0/2] bluetooth: 6lowpan: suggestions for Jukka
Date: Sat, 24 Oct 2015 16:50:54 +0200 [thread overview]
Message-ID: <1445698256-10407-1-git-send-email-alex.aring@gmail.com> (raw)
Hi,
this patch series is compile checked only and is a suggestion for Jukka which
has currently some issues with 6lowpan. These issues are page faults and I
suppose something is wrong with the memory management of the skbs.
Jukka, I also add several TODOs, take the patches and take a closer look into
that. Thanks. I mainly copied the parsing mechanism for dispatches from
802.15.4 6LoWPAN.
I hope these patches will solve your issues. If you have questions then simple
ask.
Compile tested only because I still have no btle dongle, but I think there
exists also some simulator, or? :-)
- Alex
Cc: Jukka Rissanen <jukka.rissanen@linux.intel.com>
Alexander Aring (2):
bluetooth: 6lowpan: avoid endless loop
bluetooth: 6lowpan: rework receive handling
net/bluetooth/6lowpan.c | 161 +++++++++++++++++++++++++++++-------------------
1 file changed, 96 insertions(+), 65 deletions(-)
--
2.6.1
next reply other threads:[~2015-10-24 14:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-24 14:50 Alexander Aring [this message]
2015-10-24 14:50 ` [RFC bluetooth-next 1/2] bluetooth: 6lowpan: avoid endless loop Alexander Aring
2015-10-25 20:11 ` Marcel Holtmann
2015-10-25 20:27 ` Alexander Aring
2015-10-27 9:21 ` Jukka Rissanen
2015-10-24 14:50 ` [RFC bluetooth-next 2/2] bluetooth: 6lowpan: rework receive handling Alexander Aring
2015-10-28 8:57 ` 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=1445698256-10407-1-git-send-email-alex.aring@gmail.com \
--to=alex.aring@gmail.com \
--cc=jukka.rissanen@linux.intel.com \
--cc=kernel@pengutronix.de \
--cc=linux-bluetooth@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).