[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180216181043.GA84497@rodete-desktop-imager.corp.google.com>
Date: Fri, 16 Feb 2018 10:10:44 -0800
From: Brian Norris <briannorris@...omium.org>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
Leif Liddy <leif.linux@...il.com>,
Matthias Kaehlcke <mka@...omium.org>,
Daniel Drake <drake@...lessm.com>,
Kai-Heng Feng <kai.heng.feng@...onical.com>,
Hans de Goede <hdegoede@...hat.com>,
Marcel Holtmann <marcel@...tmann.org>,
Guenter Roeck <linux@...ck-us.net>
Subject: Re: [PATCH 4.4 095/108] Bluetooth: btusb: Restore QCA Rome
suspend/resume fix with a "rewritten" version
On Fri, Feb 16, 2018 at 07:48:50AM +0100, Greg Kroah-Hartman wrote:
> On Thu, Feb 15, 2018 at 06:31:48PM -0800, Brian Norris wrote:
> > On Thu, Feb 15, 2018 at 04:17:32PM +0100, Greg Kroah-Hartman wrote:
> > > 4.4-stable review patch. If anyone has any objections, please let me know.
> >
> > Consider this an objection:
> >
> > I'm currently arguing that this is unnecessarily regressing power
> > consumption here:
> >
> > https://patchwork.kernel.org/patch/10149195/
> >
> > I'll leave it up to you what to do with this, but if this ends up in
> > Chromium OS kernels, I'm likely to revert it there...
>
> Is that patch in Linus's tree yet? If so, I'll be glad to also apply it
> here.
The link is the original patch, where I'm (too late?) complaining about
its side effects. Hans and Marcel are discussing potential alternatives.
This stuff happens in -rc kernels. But you're already ready to push it
out to -stable users? I can try to push another few reverts into Linus's
tree if that really helps, or else you can wait on pushing these to
-stable until 4.16 settles down.
Or you can ignore my objection. But I don't really like that option ;)
Brian
Powered by blists - more mailing lists