From: Alexander Aring <alex.aring@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Jukka Rissanen <jukka.rissanen@linux.intel.com>,
netdev@vger.kernel.org, linux-zigbee-devel@lists.sourceforge.net
Subject: Re: [PATCH net-next v2] 6lowpan: Moving generic compression code into 6lowpan_iphc.c
Date: Tue, 10 Dec 2013 15:19:24 +0100 [thread overview]
Message-ID: <20131210141923.GA32698@omega> (raw)
In-Reply-To: <09E9761B-6A18-4F28-9315-DD6D44C45597@holtmann.org>
On Tue, Dec 10, 2013 at 01:12:10PM +0100, Marcel Holtmann wrote:
> Hi Alexander,
>
> > thanks for working on this! Now my acked-by is correct, sry. Didn't
> > catch the debug output at first time.
> >
> >> Because the IEEE 802154 and Bluetooth share the IP header compression
> >> and uncompression code, the common code is moved to 6lowpan_iphc.c
> >> file.
> >>
> >> Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
> >> ---
> >
> > Acked-by: Alexander Aring <alex.aring@gmail.com>
>
> are you fine with us carrying these patches through bluetooth-next tree.
>
yes.
> Dave, or do you want to merge this one into net-next and then we have wireless-next pulling that in.
>
> I am trying to figure out on how we get this handled with the minimum of conflicts during the next merge window. And also at the same time get enough exposure via linux-next. The Bluetooth part is getting ready to be pushed into bluetooth-next.
>
I have some pending patches for udp iphc format and a rework of the
fragmentation api. I already rebased these patches on Jukka's patch.
So you can apply this patch in bluetooth-next.
Then I will wait until bluetooth-next is merged into net-next.
Is that okay for you?
- Alex
next prev parent reply other threads:[~2013-12-10 14:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 8:16 [PATCH net-next v2] 6lowpan: Moving generic compression code into 6lowpan_iphc.c Jukka Rissanen
2013-12-09 8:18 ` Alexander Aring
2013-12-10 12:12 ` Marcel Holtmann
2013-12-10 14:19 ` Alexander Aring [this message]
2013-12-10 17:11 ` Marcel Holtmann
2013-12-10 18:51 ` 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=20131210141923.GA32698@omega \
--to=alex.aring@gmail.com \
--cc=jukka.rissanen@linux.intel.com \
--cc=linux-zigbee-devel@lists.sourceforge.net \
--cc=marcel@holtmann.org \
--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).