Re: [PATCH v5.3-rc2] Bluetooth: hci_uart: check for missing tty operations

[Greg KH]

On Thu, Aug 01, 2019 at 01:16:39PM -0400, Sasha Levin wrote:
> On Thu, Aug 01, 2019 at 03:50:44PM +0200, Greg KH wrote:
> > On Thu, Aug 01, 2019 at 01:31:31PM +0000, Sasha Levin wrote:
> > > Hi,
> > > 
> > > [This is an automated email]
> > > 
> > > This commit has been processed because it contains a "Fixes:" tag,
> > > fixing commit: .
> > > 
> > > The bot has tested the following trees: v5.2.4, v5.1.21, v4.19.62, v4.14.134, v4.9.186, v4.4.186.
> > > 
> > > v5.2.4: Build OK!
> > > v5.1.21: Build OK!
> > > v4.19.62: Build OK!
> > > v4.14.134: Failed to apply! Possible dependencies:
> > >     25a13e382de2 ("bluetooth: hci_qca: Replace GFP_ATOMIC with GFP_KERNEL")
> > > 
> > > v4.9.186: Failed to apply! Possible dependencies:
> > >     25a13e382de2 ("bluetooth: hci_qca: Replace GFP_ATOMIC with GFP_KERNEL")
> > > 
> > > v4.4.186: Failed to apply! Possible dependencies:
> > >     162f812f23ba ("Bluetooth: hci_uart: Add Marvell support")
> > >     25a13e382de2 ("bluetooth: hci_qca: Replace GFP_ATOMIC with GFP_KERNEL")
> > >     395174bb07c1 ("Bluetooth: hci_uart: Add Intel/AG6xx support")
> > >     9e69130c4efc ("Bluetooth: hci_uart: Add Nokia Protocol identifier")
> > > 
> > > 
> > > NOTE: The patch will not be queued to stable trees until it is upstream.
> > > 
> > > How should we proceed with this patch?
> > 
> > Already fixed up by hand and queued up, your automated email is a bit
> > slow :)
> 
> /me scratches head
> 
> The patch went out two days ago:
> https://lore.kernel.org/lkml/20190730093345.25573-1-marcel@xxxxxxxxxxxx/
> 
> How did it make it upstream already?

It's in Linus's tree as b36a1552d731 ("Bluetooth: hci_uart: check for
missing tty operations") now.

thanks,

greg k-h