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
Subject: Re: [PATCH v5.3-rc2] Bluetooth: hci_uart: check for missing tty operations
Date: Thu, 1 Aug 2019 19:48:49 +0200 [thread overview]
Message-ID: <20190801174849.GA5048@kroah.com> (raw)
In-Reply-To: <20190801171639.GC17697@sasha-vm>
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
prev parent reply other threads:[~2019-08-01 17:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 9:33 [PATCH v5.3-rc2] Bluetooth: hci_uart: check for missing tty operations Marcel Holtmann
2019-07-31 2:45 ` Al Cho
2019-08-01 13:31 ` Sasha Levin
2019-08-01 13:50 ` Greg KH
2019-08-01 13:55 ` Vladis Dronov
2019-08-01 14:06 ` Greg KH
2019-08-01 14:31 ` Vladis Dronov
2019-08-01 17:16 ` Sasha Levin
2019-08-01 17:48 ` Greg KH [this message]
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=20190801174849.GA5048@kroah.com \
--to=greg@kroah.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vdronov@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).