From: Chris Friesen <chris.friesen@genband.com>
To: Wim Van Sebroeck <wim@iguana.be>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux Watchdog Mailing List <linux-watchdog@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH 1/10 v2] Generic Watchdog Timer Driver
Date: Wed, 22 Jun 2011 12:28:37 -0600 [thread overview]
Message-ID: <4E023455.8010606@genband.com> (raw)
In-Reply-To: <20110618171946.GB3441@infomag.iguana.be>
On 06/18/2011 11:19 AM, Wim Van Sebroeck wrote:
> watchdog: WatchDog Timer Driver Core - Part 1
>
> The WatchDog Timer Driver Core is a framework
> that contains the common code for all watchdog-driver's.
> It also introduces a watchdog device structure and the
> operations that go with it.
>
> This is the introduction of this framework. This part
> supports the minimal watchdog userspace API (or with
> other words: the functionality to use /dev/watchdog's
> open, release and write functionality as defined in
> the simplest watchdog API). Extra functionality will
> follow in the next set of patches.
Have you thought about callback support for systems that support a
two-stage watchdog? That way we could do something useful (preserve
system memory using kdump, for instance) rather than just getting
whacked by the hardware.
Chris
--
Chris Friesen
Software Developer
GENBAND
chris.friesen@genband.com
www.genband.com
next prev parent reply other threads:[~2011-06-22 20:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-18 17:19 [PATCH 1/10 v2] Generic Watchdog Timer Driver Wim Van Sebroeck
2011-06-18 18:58 ` Arnd Bergmann
2011-06-20 3:44 ` Randy Dunlap
2011-06-22 20:15 ` Wim Van Sebroeck
2011-06-22 12:24 ` Mark Brown
2011-06-22 19:50 ` Wim Van Sebroeck
2011-06-24 13:59 ` Arnd Bergmann
2011-06-24 19:27 ` Wim Van Sebroeck
2011-07-06 19:17 ` Wim Van Sebroeck
2011-07-06 19:26 ` Alan Cox
2011-07-06 19:30 ` Wolfram Sang
2011-06-22 18:28 ` Chris Friesen [this message]
2011-06-22 20:25 ` Wim Van Sebroeck
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=4E023455.8010606@genband.com \
--to=chris.friesen@genband.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=wim@iguana.be \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.