linux-watchdog.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: Linux Watchdog Mailing List <linux-watchdog@vger.kernel.org>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
	Fabrizio Castro <fabrizio.castro@bp.renesas.com>
Subject: Re: [RFC] watchdog: renesas_wdt: don't keep timer value during suspend/resume
Date: Tue, 4 Dec 2018 13:42:54 +0100	[thread overview]
Message-ID: <CAMuHMdUSbTFUDQDW208=gzhBP_UsQVxaGewsuHngb_Or0e+ghg@mail.gmail.com> (raw)
In-Reply-To: <20181204120146.1923-1-wsa+renesas@sang-engineering.com>

On Tue, Dec 4, 2018 at 1:02 PM Wolfram Sang
<wsa+renesas@sang-engineering.com> wrote:
> After discussing this mail thread [1] again, we concluded that giving
> userspace enough time to prepare is our favourite option. So, do not
> keep the time value when suspended but reset it when resuming.
>
> [1] https://patchwork.kernel.org/patch/10252209/
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>

Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2018-12-04 12:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-04 12:01 [RFC] watchdog: renesas_wdt: don't keep timer value during suspend/resume Wolfram Sang
2018-12-04 12:42 ` Geert Uytterhoeven [this message]
2018-12-04 12:48 ` Fabrizio Castro
2018-12-04 15:20 ` Guenter Roeck
2018-12-07 21:45   ` Wolfram Sang
2018-12-08 21:38     ` Guenter Roeck
2018-12-09 16:36       ` Wolfram Sang
2018-12-09 18:12         ` Guenter Roeck
2018-12-09 18:40           ` Wolfram Sang
2018-12-10  9:37           ` Fabrizio Castro
2018-12-10 14:23             ` Guenter Roeck
2018-12-10 14:47               ` Fabrizio Castro
2018-12-10 14:47                 ` Fabrizio Castro
2018-12-10  9:40     ` Fabrizio Castro
2018-12-10 14:49 ` Fabrizio Castro

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='CAMuHMdUSbTFUDQDW208=gzhBP_UsQVxaGewsuHngb_Or0e+ghg@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=fabrizio.castro@bp.renesas.com \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=wsa+renesas@sang-engineering.com \
    --cc=yoshihiro.shimoda.uh@renesas.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;
as well as URLs for NNTP newsgroup(s).