diff options
| author | David S. Miller <davem@davemloft.net> | 2018-12-19 08:41:45 -0800 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2018-12-19 08:41:45 -0800 |
| commit | 29d3c047b7038d7efce4f279e4d4165d69f6ccb9 (patch) | |
| tree | 72526ddc9b332675b1669bcd60d86eea3fc939e3 /drivers/net/phy/mscc.c | |
| parent | 5a862f86b8e86562fc8532160c5530a13e1e944b (diff) | |
| parent | 1629db9c75342325868243d6bca5853017d91cf8 (diff) | |
Merge branch 'for-upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next
Johan Hedberg says:
====================
pull request: bluetooth-next 2018-12-19
Here's the main bluetooth-next pull request for 4.21:
- Multiple fixes & improvements for Broadcom-based controllers
- New USB ID for an Intel controller
- Support for new Broadcom controller variants
- Use DEFINE_SHOW_ATTRIBUTE to simplify debugfs code
- Eliminate confusing "last event is not cmd complete" warning message
- Added vendor suspend/resume support for H:5 (3-Wire UART) controllers
- Various other smaller improvements & fixes
Please let me know if there are any issues pulling. Thanks.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/phy/mscc.c')
0 files changed, 0 insertions, 0 deletions