mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] Tegra30+ CPU suspend-resume bug-fixes
Date: Tue, 23 Jul 2019 04:28:35 +0300	[thread overview]
Message-ID: <f81a974b-4e64-9b66-0399-519480f53c31@gmail.com> (raw)
In-Reply-To: <20190707230358.10672-1-digetx@gmail.com>

08.07.2019 2:03, Dmitry Osipenko пишет:
> Hello,
> 
> This small series addresses two suspend-resume bugs: one affects Tegra30+
> due to a typo in the code, other fixes CPU hang on Tegra30 specifically.
> 
> Please review and apply, thanks!
> 
> Dmitry Osipenko (2):
>   ARM: tegra: Fix FLOW_CTLR_HALT register clobbering by tegra_resume()
>   ARM: tegra: Use WFE for power-gating on Tegra30
> 
>  arch/arm/mach-tegra/reset-handler.S |  6 +++---
>  arch/arm/mach-tegra/sleep-tegra30.S |  4 +++-
>  drivers/soc/tegra/flowctrl.c        | 19 +++++++++++++++++--
>  3 files changed, 23 insertions(+), 6 deletions(-)
> 

Hello Peter,

We were talking about these fixes on the IRC not so long time ago, does
it look good to you? Care to give an ACK?

  parent reply	other threads:[~2019-07-23  1:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-07 23:03 Dmitry Osipenko
2019-07-07 23:03 ` [PATCH v1 1/2] ARM: tegra: Fix FLOW_CTLR_HALT register clobbering by tegra_resume() Dmitry Osipenko
2019-07-07 23:03 ` [PATCH v1 2/2] ARM: tegra: Use WFE for power-gating on Tegra30 Dmitry Osipenko
2019-07-23  1:28 ` Dmitry Osipenko [this message]
2019-07-25  9:40   ` [PATCH v1 0/2] Tegra30+ CPU suspend-resume bug-fixes Peter De Schrijver
2019-07-25 13:43     ` Dmitry Osipenko

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=f81a974b-4e64-9b66-0399-519480f53c31@gmail.com \
    --to=digetx@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=pdeschrijver@nvidia.com \
    --cc=thierry.reding@gmail.com \
    /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

all inboxes | Powered by JetHome®