From: David Miller <davem@davemloft.net>
To: alex.aring@gmail.com
Cc: alex.bluesman.smirnov@gmail.com, dbaryshkov@gmail.com,
linux-zigbee-devel@lists.sourceforge.net, netdev@vger.kernel.org,
martin.townsend@xsilon.com
Subject: Re: [PATCH net-next v6 0/8] 6lowpan: reimplementation of fragmentation handling
Date: Fri, 28 Feb 2014 17:13:09 -0500 (EST) [thread overview]
Message-ID: <20140228.171309.2174993179721650384.davem@davemloft.net> (raw)
In-Reply-To: <1393569170-25722-1-git-send-email-alex.aring@gmail.com>
From: Alexander Aring <alex.aring@gmail.com>
Date: Fri, 28 Feb 2014 07:32:42 +0100
> this patch series reimplementation the fragmentation handling of 6lowpan
> accroding to rfc4944 [1].
Looks great, series applied, thanks Alexander.
prev parent reply other threads:[~2014-02-28 22:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 6:32 [PATCH net-next v6 0/8] 6lowpan: reimplementation of fragmentation handling Alexander Aring
2014-02-28 6:32 ` [PATCH net-next v6 1/8] 6lowpan: add frag information struct Alexander Aring
[not found] ` <1393569170-25722-1-git-send-email-alex.aring-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-02-28 6:32 ` [PATCH net-next v6 2/8] 6lowpan: add uncompress header size function Alexander Aring
2014-02-28 6:32 ` [PATCH net-next v6 3/8] 6lowpan: fix fragmentation on sending side Alexander Aring
2014-02-28 6:32 ` [PATCH net-next v6 4/8] 6lowpan: change tag type to __be16 Alexander Aring
2014-02-28 6:32 ` [PATCH net-next v6 5/8] 6lowpan: move 6lowpan.c to 6lowpan_rtnl.c Alexander Aring
2014-02-28 6:32 ` [PATCH net-next v6 6/8] 6lowpan: fix some checkpatch issues Alexander Aring
2014-02-28 6:32 ` [PATCH net-next v6 7/8] net: ns: add ieee802154_6lowpan namespace Alexander Aring
2014-02-28 6:32 ` [PATCH net-next v6 8/8] 6lowpan: handling 6lowpan fragmentation via inet_frag api Alexander Aring
2014-02-28 22:13 ` David Miller [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=20140228.171309.2174993179721650384.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alex.aring@gmail.com \
--cc=alex.bluesman.smirnov@gmail.com \
--cc=dbaryshkov@gmail.com \
--cc=linux-zigbee-devel@lists.sourceforge.net \
--cc=martin.townsend@xsilon.com \
--cc=netdev@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).