From: tony@atomide•com (Tony Lindgren)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: OMAP2+: omap_device: drop broken RPM status update from suspend_noirq
Date: Thu, 10 Aug 2017 08:08:12 -0700 [thread overview]
Message-ID: <20170810150812.GB8569@atomide.com> (raw)
In-Reply-To: <20170726083521.GE27516@localhost>
* Johan Hovold <johan@kernel•org> [170726 01:36]:
> On Wed, Jul 26, 2017 at 01:17:17AM -0700, Tony Lindgren wrote: > * Johan Hovold <johan@kernel•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@ti•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
next prev parent reply other threads:[~2017-08-10 15:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 9:52 [PATCH] ARM: OMAP2+: omap_device: drop broken RPM status update from suspend_noirq Johan Hovold
2017-07-24 22:16 ` Grygorii Strashko
2017-07-25 7:10 ` Tony Lindgren
2017-07-25 8:56 ` Tony Lindgren
2017-07-25 17:41 ` Grygorii Strashko
2017-07-25 8:24 ` Johan Hovold
2017-07-25 17:48 ` Grygorii Strashko
2017-07-26 7:50 ` Johan Hovold
2017-07-26 8:17 ` Tony Lindgren
2017-07-26 8:35 ` Johan Hovold
2017-08-10 15:08 ` Tony Lindgren [this message]
2017-07-25 8:55 ` Tony Lindgren
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=20170810150812.GB8569@atomide.com \
--to=tony@atomide$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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