From: Vladis Dronov <vdronov@redhat.com>
To: Greg KH <greg@kroah.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
Subject: Re: [PATCH v5.3-rc2] Bluetooth: hci_uart: check for missing tty operations
Date: Thu, 1 Aug 2019 10:31:26 -0400 (EDT) [thread overview]
Message-ID: <2057215544.6298959.1564669886072.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20190801140639.GB31375@kroah.com>
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
next prev parent reply other threads:[~2019-08-01 14:31 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 [this message]
2019-08-01 17:16 ` Sasha Levin
2019-08-01 17:48 ` Greg KH
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=2057215544.6298959.1564669886072.JavaMail.zimbra@redhat.com \
--to=vdronov@redhat.com \
--cc=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 \
/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).