All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: linux-wpan@vger.kernel.org
Cc: kernel@pengutronix.de, Alexander Aring <alex.aring@gmail.com>
Subject: [PATCH bluetooth-next 0/3] ieee802154: 6lowpan: separate receive/transmit functionality
Date: Tue, 23 Dec 2014 11:30:08 +0100	[thread overview]
Message-ID: <1419330611-29410-1-git-send-email-alex.aring@gmail.com> (raw)

Hi,

this patch series based on "ieee802154: structural directory changes" and
contains splitting of receive/transmit functionality in separate tx and rx
files. At least we rename the 6lowpan_rtnl to core which contains core
functionality for 802.15.4 6LoWPAN.

Alexander Aring (3):
  ieee802154: 6lowpan: move receive functionality
  ieee802154: 6lowpan: move transmit functionality
  ieee802154: 6lowpan: rename to core

 net/ieee802154/6lowpan/6lowpan_i.h    |  31 ++
 net/ieee802154/6lowpan/6lowpan_rtnl.c | 729 ----------------------------------
 net/ieee802154/6lowpan/Makefile       |   2 +-
 net/ieee802154/6lowpan/core.c         | 304 ++++++++++++++
 net/ieee802154/6lowpan/rx.c           | 171 ++++++++
 net/ieee802154/6lowpan/tx.c           | 271 +++++++++++++
 6 files changed, 778 insertions(+), 730 deletions(-)
 delete mode 100644 net/ieee802154/6lowpan/6lowpan_rtnl.c
 create mode 100644 net/ieee802154/6lowpan/core.c
 create mode 100644 net/ieee802154/6lowpan/rx.c
 create mode 100644 net/ieee802154/6lowpan/tx.c

-- 
2.2.0


             reply	other threads:[~2014-12-23 10:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-23 10:30 Alexander Aring [this message]
2014-12-23 10:30 ` [PATCH bluetooth-next 1/3] ieee802154: 6lowpan: move receive functionality Alexander Aring
2014-12-23 10:30 ` [PATCH bluetooth-next 2/3] ieee802154: 6lowpan: move transmit functionality Alexander Aring
2014-12-23 10:30 ` [PATCH bluetooth-next 3/3] ieee802154: 6lowpan: rename to core Alexander Aring
2014-12-23 10:39 ` [PATCH bluetooth-next 0/3] ieee802154: 6lowpan: separate receive/transmit functionality Varka Bhadram

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=1419330611-29410-1-git-send-email-alex.aring@gmail.com \
    --to=alex.aring@gmail.com \
    --cc=kernel@pengutronix.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.