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?
-- Thanks, Sasha
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 :)
greg k-h
Thank you, Greg!
I've just noticed the patch landed in the upstream and was going to start stable backports, but it appeared you've already done this.
So, not only automated mailers are slow :)
Best regards, Vladis Dronov | Red Hat, Inc. | The Core Kernel | Senior Software Engineer
----- Original Message -----
From: "Greg KH" greg@kroah.com To: "Sasha Levin" sashal@kernel.org Cc: "Marcel Holtmann" marcel@holtmann.org, "Vladis Dronov" vdronov@redhat.com, torvalds@linux-foundation.org, linux-kernel@vger.kernel.org, linux-bluetooth@vger.kernel.org, stable@vger.kernel.org Sent: Thursday, August 1, 2019 3:50:44 PM Subject: Re: [PATCH v5.3-rc2] Bluetooth: hci_uart: check for missing tty operations
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 :)
greg k-h
On Thu, Aug 01, 2019 at 09:55:55AM -0400, Vladis Dronov wrote:
Thank you, Greg!
I've just noticed the patch landed in the upstream and was going to start stable backports, but it appeared you've already done this.
Verifying that I got the 4.4.y and 4.9.y and 4.14.y backports done properly would be good, as I took a guess at them :)
thanks,
greg k-h
Hello, Greg, all,
I've just double-checked your backports, indeed, they are fine.
Check for operations is not added for protocols which does not use these operations. Thanks!
Best regards, Vladis Dronov | Red Hat, Inc. | The Core Kernel | Senior Software Engineer
----- Original Message -----
From: "Greg KH" greg@kroah.com To: "Vladis Dronov" vdronov@redhat.com Cc: "Sasha Levin" sashal@kernel.org, "Marcel Holtmann" marcel@holtmann.org, torvalds@linux-foundation.org, linux-kernel@vger.kernel.org, linux-bluetooth@vger.kernel.org, stable@vger.kernel.org Sent: Thursday, August 1, 2019 4:06:39 PM Subject: Re: [PATCH v5.3-rc2] Bluetooth: hci_uart: check for missing tty operations
On Thu, Aug 01, 2019 at 09:55:55AM -0400, Vladis Dronov wrote:
Thank you, Greg!
I've just noticed the patch landed in the upstream and was going to start stable backports, but it appeared you've already done this.
Verifying that I got the 4.4.y and 4.9.y and 4.14.y backports done properly would be good, as I took a guess at them :)
thanks,
greg k-h
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@holtmann.org/
How did it make it upstream already?
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@holtmann.org/
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
linux-stable-mirror@lists.linaro.org