From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johan Hedberg Subject: Re: pull request: bluetooth-next 2015-05-04 Date: Wed, 6 May 2015 20:21:02 +0200 Message-ID: <20150506182102.GA16001@t440s> References: <20150504093436.GB9096@t440s.lan> <20150504.153627.768616765733905013.davem@davemloft.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: David Miller Return-path: Content-Disposition: inline In-Reply-To: <20150504.153627.768616765733905013.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org> Sender: linux-bluetooth-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: netdev.vger.kernel.org Hi Dave, On Mon, May 04, 2015, David Miller wrote: > From: Johan Hedberg > Date: Mon, 4 May 2015 12:34:36 +0300 > > > Here's the first bluetooth-next pull request for 4.2: > > > > - Various fixes for at86rf230 driver > > - ieee802154: trace events support for rdev->ops > > - HCI UART driver refactoring > > - New Realtek IDs added to btusb driver > > - Off-by-one fix for rtl8723b in btusb driver > > - Refactoring of btbcm driver for both UART & USB use > > > > Please let me know if there are any issues pulling. Thanks. > > Pulled, thanks Johan. Seems you pulled this into net.git and not net-next.git? Meanwhile, the bluetooth.git request I also made on the 4th is still untouched. Johan