From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Perches Subject: Re: [PATCH V2 2/3] bluetooth: Convert BT_ERR/BT_INFO to bt_err/bt_info Date: Fri, 17 Feb 2012 10:12:22 -0800 Message-ID: <1329502342.584.4.camel@joe2Laptop> References: <6737e9dc6d2528f9c94c122709a40e4c23c9477a.1329461203.git.joe@perches.com> <1329468018.28848.133.camel@aeonflux> <20120217094110.GB12814@x220> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Marcel Holtmann , "Gustavo F. Padovan" , "David S. Miller" , linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org To: Johan Hedberg Return-path: In-Reply-To: <20120217094110.GB12814@x220> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Fri, 2012-02-17 at 11:41 +0200, Johan Hedberg wrote: > Patches 2/3 and 3/3 have never actually made it to the linux-bluetooth > list (I've never seen them and they're not visible in the archives > either). Doing the split like Marcel proposes would probably solve the > issue since I'm guessing the large message size is to blame. Hi Johan. I'm not subscribed to linux-bluetooth. linux-bluetooth is a vger list so I would expect the maximum message size to be no different than lkml though. These messages did get through to netdev and lkml. http://patchwork.ozlabs.org/patch/141748/ http://patchwork.ozlabs.org/patch/141749/ You're not listed as a bluetooth maintainer. Should you be? Do you want the original patch set sent directly to you?