linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@roeck-us.net (Guenter Roeck)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] watchdog: Add reboot API
Date: Fri, 9 May 2014 17:53:20 -0700	[thread overview]
Message-ID: <20140510005320.GA1319@roeck-us.net> (raw)
In-Reply-To: <536D74E3.8010609@infradead.org>

On Fri, May 09, 2014 at 05:37:55PM -0700, Randy Dunlap wrote:
> On 05/09/2014 05:31 PM, Guenter Roeck wrote:
> > Some hardware implements reboot through its watchdog hardware, for example
> > by triggering a watchdog timeout or by writing into its watchdog register
> > set. Platform specific code starts to spread into watchdog drivers,
> > typically by setting pointers to a callback function which is then called
> > from the architecture's reset handler.
> 
> No updates to Documentation/watchdog/ ?
> 

You are absolutely right, I missed that completely.
Will follow in v3.

Thanks,
Guenter

  reply	other threads:[~2014-05-10  0:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-10  0:31 [PATCH v2 0/5] watchdog: Add reboot API Guenter Roeck
2014-05-10  0:31 ` [PATCH v2 1/5] watchdog: Add API to trigger reboots Guenter Roeck
2014-05-10  0:31 ` [PATCH v2 2/5] arm64: Support reboot through watchdog subsystem Guenter Roeck
2014-05-15  1:37   ` Guenter Roeck
2014-05-15  9:09     ` Will Deacon
2014-05-15 16:50       ` Guenter Roeck
2014-05-10  0:31 ` [PATCH v2 3/5] arm: " Guenter Roeck
2014-05-15  1:37   ` Guenter Roeck
2014-05-10  0:31 ` [PATCH 4/5] watchdog: moxart: Register reboot handler with " Guenter Roeck
2014-05-10  0:31 ` [PATCH v2 5/5] watchdog: sunxi: " Guenter Roeck
2014-05-10  0:37 ` [PATCH v2 0/5] watchdog: Add reboot API Randy Dunlap
2014-05-10  0:53   ` Guenter Roeck [this message]
2014-05-10 16:23   ` [PATCH 6/5] watchdog: Document " Guenter Roeck
2014-05-10 21:01     ` Randy Dunlap

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=20140510005320.GA1319@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).