From: Alexander Aring <alex.aring@gmail.com>
To: Phoebe Buckheister <phoebe.buckheister@itwm.fraunhofer.de>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
linux-zigbee-devel@lists.sourceforge.net
Subject: Re: [Linux-zigbee-devel] [PATCH net-next] ieee802154: properly unshare skbs in ieee802154 *_rcv functions
Date: Mon, 17 Mar 2014 17:21:01 +0100 [thread overview]
Message-ID: <20140317162058.GA10857@omega> (raw)
In-Reply-To: <1395070888-1130-1-git-send-email-phoebe.buckheister@itwm.fraunhofer.de>
Hi Phoebe,
looks interesting but doens't apply on current net-next for me. :(
I didn't test it yet.
line 444 in this patch looks different than current net-next one.
Maybe you can respin this patch before net-next is closed. Thanks.
- Alex
next prev parent reply other threads:[~2014-03-17 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 15:41 [PATCH net-next] ieee802154: properly unshare skbs in ieee802154 *_rcv functions Phoebe Buckheister
2014-03-17 16:21 ` Alexander Aring [this message]
2014-03-17 16:44 ` [Linux-zigbee-devel] " Phoebe Buckheister
2014-03-18 20:02 ` 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=20140317162058.GA10857@omega \
--to=alex.aring@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-zigbee-devel@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=phoebe.buckheister@itwm.fraunhofer.de \
/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).