From: David Miller <davem@davemloft.net>
To: johan.hedberg@gmail.com
Cc: netdev@vger.kernel.org, linux-bluetooth@vger.kernel.org
Subject: Re: pull request: bluetooth-next 2015-05-04
Date: Mon, 04 May 2015 15:36:27 -0400 (EDT) [thread overview]
Message-ID: <20150504.153627.768616765733905013.davem@davemloft.net> (raw)
In-Reply-To: <20150504093436.GB9096@t440s.lan>
From: Johan Hedberg <johan.hedberg@gmail.com>
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.
next prev parent reply other threads:[~2015-05-04 19:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 9:34 pull request: bluetooth-next 2015-05-04 Johan Hedberg
2015-05-04 19:36 ` David Miller [this message]
[not found] ` <20150504.153627.768616765733905013.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2015-05-06 18:21 ` Johan Hedberg
2015-05-09 19:51 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150504.153627.768616765733905013.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox