From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f182.google.com ([209.85.212.182]:33118 "EHLO mail-wi0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751277AbaISJGU (ORCPT ); Fri, 19 Sep 2014 05:06:20 -0400 Date: Fri, 19 Sep 2014 11:06:13 +0200 From: Alexander Aring Subject: Re: [PATCH bluetooth-next v2 0/3] cleanup for mrf24j40 driver Message-ID: <20140919090611.GA17051@omega> References: <1411101911-12462-1-git-send-email-varkab@cdac.in> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1411101911-12462-1-git-send-email-varkab@cdac.in> Sender: linux-wpan-owner@vger.kernel.org List-ID: To: Varka Bhadram Cc: linux-wpan@vger.kernel.org, linux-bluetooth@vger.kernel.org, alan@signal11.us, Varka Bhadram Hi Varka, nice to read you again. :-) I already thought that I was maybe a little bit too harsh to you for explaining changing dev->add_len during runtime will occur in unexcept behaviour. Sorry. Nevertheless welcome back. I want to apply it when Alan finally sends a "Acked-by: ...", but why is this tagged with bluetooth-next? There are other mrf24j40 patches around and it's better to send this in a whole patch series when all patches are on wpan-next/testing. Then I will send these patches to bluetooth-next. When applied I will rebase the wpan-next/master to bluetooth-next/master. Only 6LOWPAN GENERIC patches should be send to bluetooth-next. - Alex