[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170810150812.GB8569@atomide.com>
Date: Thu, 10 Aug 2017 08:08:12 -0700
From: Tony Lindgren <tony@...mide.com>
To: Johan Hovold <johan@...nel.org>
Cc: Grygorii Strashko <grygorii.strashko@...com>,
Russell King <linux@...linux.org.uk>,
linux-omap@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
Alan Stern <stern@...land.harvard.edu>,
Dave Gerlach <d-gerlach@...com>,
Kevin Hilman <khilman@...libre.com>,
Nishanth Menon <nm@...com>,
"Rafael J . Wysocki" <rjw@...ysocki.net>,
Ulf Hansson <ulf.hansson@...aro.org>
Subject: Re: [PATCH] ARM: OMAP2+: omap_device: drop broken RPM status update
from suspend_noirq
* Johan Hovold <johan@...nel.org> [170726 01:36]:
> On Wed, Jul 26, 2017 at 01:17:17AM -0700, Tony Lindgren wrote: > * Johan Hovold <johan@...nel.org> [170726 00:51]:
> > > On Tue, Jul 25, 2017 at 12:48:40PM -0500, Grygorii Strashko wrote:
> > > > So, thank you for your patches and sorry for the noise.
> > > >
> > > > Tested-by: Grygorii Strashko <grygorii.strashko@...com>
> > >
> > > Thanks for testing.
> >
> > So does the patch description need updating?
>
> I don't think so.
>
> I did notice that I left out a "would" in the final sentence
>
> "and either way, any such calls *would* have been causing
> crashes since 4.10"
>
> which perhaps you could add when applying?
>
> > And this is needed as a fix for the -rc cycle in addition to your musb
> > patch?
>
> Unlike the musb patch, this one is not critical and could possibly wait
> for 4.14. But since all it does is to get rid of a (since 4.10) broken
> state update, and thereby those warning messages on suspend, I'd say
> it's -rc material.
Applying into omap-for-v4.13/fixes finally thanks.
Tony
Powered by blists - more mailing lists