From: Tony Lindgren <tony@atomide.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Sekhar Nori <nsekhar@ti.com>, Kevin Hilman <khilman@kernel.org>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Dinh Nguyen <dinguyen@kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH 0/3] ARM: PM: Drop useless checks for PM_SUSPEND_STANDBY
Date: Mon, 6 Mar 2017 10:38:57 -0800 [thread overview]
Message-ID: <20170306183856.GM20572@atomide.com> (raw)
In-Reply-To: <20170217164018.GE21809@atomide.com>
* Tony Lindgren <tony@atomide.com> [170217 08:41]:
> * Geert Uytterhoeven <geert+renesas@glider.be> [170217 08:12]:
> > Hi all,
> >
> > The system suspend implementations for DaVinci, OMAP, and SoCFPGA use
> > the standard suspend_valid_only_mem() for their
> > platform_suspend_ops.valid() callbacks. Hence their
> > platform_suspend_ops.enter() callbacks will never be called with state
> > equal to PM_SUSPEND_STANDBY, and checks for this can thus be removed.
> >
> > Thanks for your comments!
>
> Seems safe to remove:
>
> Acked-by: Tony Lindgren <tony@atomide.com>
Sounds like you wanted me to pick this up so applying the
omap related patch into omap-for-v4.12/soc.
Thanks,
Tony
prev parent reply other threads:[~2017-03-06 18:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 16:10 [PATCH 0/3] ARM: PM: Drop useless checks for PM_SUSPEND_STANDBY Geert Uytterhoeven
2017-02-17 16:10 ` [PATCH 1/3] ARM: davinci: PM: Drop useless check " Geert Uytterhoeven
2017-02-20 8:30 ` Sekhar Nori
2017-02-20 8:40 ` Geert Uytterhoeven
2017-02-21 8:57 ` Sekhar Nori
2017-02-17 16:10 ` [PATCH 2/3] ARM: OMAP: PM: Drop useless checks " Geert Uytterhoeven
2017-02-17 16:10 ` [PATCH 3/3] ARM: socfpga: PM: Drop useless check " Geert Uytterhoeven
2017-02-19 20:15 ` Dinh Nguyen
2017-02-17 16:40 ` [PATCH 0/3] ARM: PM: Drop useless checks " Tony Lindgren
2017-03-06 18:38 ` Tony Lindgren [this message]
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=20170306183856.GM20572@atomide.com \
--to=tony@atomide.com \
--cc=aaro.koskinen@iki.fi \
--cc=dinguyen@kernel.org \
--cc=geert+renesas@glider.be \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=rjw@sisk.pl \
/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).