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 ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ Linux-zigbee-devel mailing list Linux-zigbee-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel
