[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171223091836.GF13832@kroah.com>
Date: Sat, 23 Dec 2017 10:18:36 +0100
From: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
To: Brian Norris <briannorris@...omium.org>
Cc: Guenter Roeck <linux@...ck-us.net>,
Matthias Kaehlcke <mka@...omium.org>,
"Ghorai, Sukumar" <sukumar.ghorai@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"stable@...r.kernel.org" <stable@...r.kernel.org>,
"Bag, Amit K" <amit.k.bag@...el.com>,
Oliver Neukum <oneukum@...e.com>,
Marcel Holtmann <marcel@...tmann.org>,
Todd Broch <tbroch@...omium.org>,
Rajat Jain <rajatja@...omium.org>,
Miao Chou <mcchou@...omium.org>,
"Rao Pv, Sadashiva" <sadashiva.rao.pv@...el.com>
Subject: Re: [PATCH 4.4 009/115] Bluetooth: btusb: driver to enable the
usb-wakeup feature
On Fri, Dec 22, 2017 at 09:37:48AM -0800, Brian Norris wrote:
> > included in 4.14-rc1, so something needs to be done in Linus's tree to
> > resolve this issue, otherwise people will hit this as a regression when
> > moving to 4.14 or newer.
>
> Well, I wouldn't object to reverting it in Linus' tree too, since AFAIK,
> this is something that can be configured by user-space policy, no? And
> that way, no user space is surprised by the sudden additional
> requirements on managing bluetooth wakeup.
I agree, please work with the bluetooth developers to make this happen.
They seem to be ignoring patches right now, so you might have to kick
them a few times :(
thanks
greg k-h
Powered by blists - more mailing lists