linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Martin Townsend <martin.townsend@xsilon.com>
Cc: linux-zigbee-devel@lists.sourceforge.net,
	linux-bluetooth@vger.kernel.org, linux-wpan@vger.kernel.org,
	Marcel Holtmann <marcel@holtmann.org>
Subject: Re: [PATCH v2 bluetooth-next] Simplify lowpan receive path so skb is freed in lowpan_rcv when dropped.
Date: Mon, 4 Aug 2014 10:13:19 +0200	[thread overview]
Message-ID: <20140804081317.GA9272@omega> (raw)
In-Reply-To: <53DCE75C.2030305@xsilon.com>

Hi Martin,

this patch doesn't apply for me on current bluetooth-next. Can you
respin the patch? Thanks.

- Alex

  reply	other threads:[~2014-08-04  8:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-02 13:27 [PATCH v2 bluetooth-next] Simplify lowpan receive path so skb is freed in lowpan_rcv when dropped Martin Townsend
2014-08-04  8:13 ` Alexander Aring [this message]
2014-08-21  6:30 ` [Linux-zigbee-devel] " Martin Townsend
2014-08-21  8:39 ` Alexander Aring
2014-08-21 13:24   ` Marcel Holtmann
2014-08-27 20:49     ` Martin Townsend
2014-08-28  4:47       ` Alexander Aring
2014-08-28  5:19         ` Alexander Aring
2014-09-08 10:40       ` Alexander Aring
2014-09-08 18:13         ` Martin Townsend
2014-09-08 18:36           ` Alexander Aring
2014-09-08 18:55             ` Alexander Aring
2014-09-09  9:28               ` Martin Townsend
2014-09-09  9:46                 ` Alexander Aring
2014-09-09  9:59                   ` Alexander Aring
2014-09-09 10:17                   ` Martin Townsend
2014-09-09 10:47                     ` Alexander Aring
2014-09-09 11:13                       ` Martin Townsend
2014-09-09 13:44                   ` Marcel Holtmann
2014-09-10  0:18                     ` Alexander Aring
2014-09-09  8:59             ` Martin Townsend

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=20140804081317.GA9272@omega \
    --to=alex.aring@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-wpan@vger.kernel.org \
    --cc=linux-zigbee-devel@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    --cc=martin.townsend@xsilon.com \
    /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).