Hi Marcel,

On Fri, 16 Nov 2018 20:58:24 +0100
Marcel Holtmann <marcel@holtmann.org> wrote:

> Hi Andreas,
> 
> >> Btw. I see nothing standing in the way of merging btuart.c driver and then go from there. Either I dig this out and submit or someone else does.
> >>   
> > Do you mean this?
> > https://patchwork.kernel.org/patch/10490651/  
> 
> yes, that one.
> 
Hmm, there seemed to be nothing in the pull requests regarding btuart.
Did you change plans?

commit 29d3c047b7038d7efce4f279e4d4165d69f6ccb9
Merge: 5a862f86b8e8 1629db9c7534
Author: David S. Miller <davem@davemloft.net>
Date:   Wed Dec 19 08:41:45 2018 -0800

    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.


Regards,
Andreas