Return-Path: Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: [PATCH][linux-bluetooth 2/3] 6lowpan: Move skb delivery from IPHC. From: Marcel Holtmann In-Reply-To: <20140911081808.GA19675@omega> Date: Thu, 11 Sep 2014 07:11:31 -0700 Cc: Martin Townsend , linux-zigbee-devel@lists.sourceforge.net, linux-bluetooth@vger.kernel.org, linux-wpan@vger.kernel.org, Martin Townsend Message-Id: <1C268090-606B-45BF-8B47-7A3B35886F10@holtmann.org> References: <1410357968-27051-1-git-send-email-martin.townsend@xsilon.com> <1410357968-27051-4-git-send-email-martin.townsend@xsilon.com> <20140911081808.GA19675@omega> To: Alexander Aring Sender: linux-wpan-owner@vger.kernel.org List-ID: Hi Alex, >> Passing the skb from 6lowpan up to the higher layers is not a >> function of IPHC. By moving it out of IPHC we also remove the >> need to support error code returns with NET_RX codes. >> It also makes the lowpan_rcv function more extendable as we >> can support more compression schemes. >> > > I will ack this. But please sperate this patch in two. First renaming > the function namens and then removing deliver callback. > > btw. The correct tag is bluetooth not linux-bluetooth, or bluetooth-next. > > > > Also this doesn't fix anything? Then this is for bluetooth-next. I know > this depends on the Patch 1/3. Marcel, do you have any a nice solution > about this, that we can deal with huge fixes in bluetooth and new features > for bluetooth-next. Or simple wait when it's merged? we need to get it into wireless first and pulled by davem. After that I can ask John to pull wireless tree back into wireless-next. Regards Marcel