From: Alexander Aring <alex.aring@gmail.com>
To: linux-wpan@vger.kernel.org
Cc: linux-bluetooth@vger.kernel.org, kernel@pengutronix.de,
marcel@holtmann.org
Subject: Re: [PATCH bluetooth-next 0/2] 6lowpan: iphc: cleanups
Date: Wed, 25 Nov 2015 14:23:24 +0100 [thread overview]
Message-ID: <20151125132322.GA1920@omega> (raw)
In-Reply-To: <1447786441-17845-1-git-send-email-alex.aring@gmail.com>
On Tue, Nov 17, 2015 at 07:53:59PM +0100, Alexander Aring wrote:
> Hi,
>
> These two patches are from the current RFC of stateful compression support.
> It has nothing todo with stateful compression, I send it now as PATCH so
> it can be applied before.
>
ping :-)
- Alex
prev parent reply other threads:[~2015-11-25 13:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 18:53 [PATCH bluetooth-next 0/2] 6lowpan: iphc: cleanups Alexander Aring
2015-11-17 18:54 ` [PATCH bluetooth-next 1/2] 6lowpan: iphc: add check for reserved values Alexander Aring
2015-11-17 21:04 ` Stefan Schmidt
2015-11-17 18:54 ` [PATCH bluetooth-next 2/2] 6lowpan: iphc: remove handling when dam is zero Alexander Aring
2015-11-17 21:04 ` Stefan Schmidt
2015-11-25 13:23 ` Alexander Aring [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=20151125132322.GA1920@omega \
--to=alex.aring@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=marcel@holtmann.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).