From: Alexander Aring <alex.aring@gmail.com>
To: davem@davemloft.net
Cc: dbaryshkov@gmail.com, alex.bluesman.smirnov@gmail.com,
linux-zigbee-devel@lists.sourceforge.net, netdev@vger.kernel.org,
martin.townsend@xsilon.com
Subject: Re: [PATCH RFC net-next 0/6] 6lowpan: reimplementation of fragmentation handling
Date: Thu, 20 Feb 2014 09:46:43 +0100 [thread overview]
Message-ID: <20140220084642.GA29611@omega> (raw)
In-Reply-To: <20140218195824.GA935@omega>
Dear David Miller,
looks this patch stack okay for you?
I don't want to be annoying, I worked a long time on these series and I would
be happy if these patches will apply into mainline. Then I can take the
next TODO on my long "6lowpan/ieee802154" list.
- Alex
next prev parent reply other threads:[~2014-02-20 8:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-16 8:34 [PATCH RFC net-next 0/6] 6lowpan: reimplementation of fragmentation handling Alexander Aring
[not found] ` <1392539668-2349-1-git-send-email-alex.aring-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-02-16 8:34 ` [PATCH RFC net-next 1/6] 6lowpan: add frag information struct Alexander Aring
2014-02-16 8:34 ` [PATCH RFC net-next 2/6] 6lowpan: fix fragmentation on sending side Alexander Aring
2014-02-16 8:34 ` [PATCH RFC net-next 3/6] 6lowpan: move 6lowpan.c to 6lowpan_rtnl.c Alexander Aring
2014-02-16 8:34 ` [PATCH RFC net-next 4/6] 6lowpan: fix some checkpatch issues Alexander Aring
2014-02-16 8:34 ` [PATCH RFC net-next 5/6] net: ns: add ieee802154_6lowpan namespace Alexander Aring
2014-02-16 8:34 ` [PATCH RFC net-next 6/6] 6lowpan: handling 6lowpan fragmentation via inet_frag api Alexander Aring
2014-02-18 19:58 ` [PATCH RFC net-next 0/6] 6lowpan: reimplementation of fragmentation handling Alexander Aring
2014-02-20 8:46 ` Alexander Aring [this message]
2014-02-20 18:10 ` David Miller
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=20140220084642.GA29611@omega \
--to=alex.aring@gmail.com \
--cc=alex.bluesman.smirnov@gmail.com \
--cc=davem@davemloft.net \
--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 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.