From: Padraig Brady <padraig.brady@corvil.com>
To: Wim Van Sebroeck <wim@iguana.be>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Watchdog drivers
Date: Mon, 14 Oct 2002 10:29:29 +0100 [thread overview]
Message-ID: <3DAA8E79.70609@corvil.com> (raw)
In-Reply-To: 20021013194041.A15609@medelec.uia.ac.be
Wim Van Sebroeck wrote:
> Hi Linus,
>
> I'm reviewing the different watchdog drivers and started porting the features
> that have been added in the 2.4 kernel to the 2.5 development kernel.
> I now wondered if it would make sence to put all watchdog drivers in
> drivers/char/watchdog/ instead of in drivers/char ?
> Please comments.
Well I think it's a good idea, as you can easily see what
watchdogs are supported rather than referring to the (currently
out of date) docs:
http://www.cs.helsinki.fi/linux/linux-kernel/2002-02/0713.html
Pádraig.
next prev parent reply other threads:[~2002-10-14 9:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-13 17:40 Watchdog drivers Wim Van Sebroeck
2002-10-13 19:01 ` Russell King
2002-10-13 22:31 ` Randy.Dunlap
2002-10-13 22:43 ` Russell King
2002-10-13 23:17 ` Randy.Dunlap
2002-10-14 1:57 ` Rob Radez
2002-10-14 8:12 ` Wim Van Sebroeck
2002-10-14 12:22 ` Dave Jones
2002-10-14 12:41 ` Wim Van Sebroeck
2002-10-14 13:04 ` Dave Jones
2002-10-14 15:11 ` Rob Radez
2002-10-15 9:35 ` David Woodhouse
2002-10-15 11:20 ` Dave Jones
2002-10-14 15:58 ` Randy.Dunlap
2002-10-14 9:29 ` Padraig Brady [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-14 15:51 Matt_Domsch
2002-10-14 16:40 ` Wim Van Sebroeck
2002-10-14 19:12 ` Matt Domsch
2002-10-15 9:25 ` Adrian Bunk
2002-10-15 17:26 ` Wim Van Sebroeck
2002-10-16 21:36 ` Wim Van Sebroeck
2002-11-06 13:10 ` Wim Van Sebroeck
2002-10-15 12:57 Matt_Domsch
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=3DAA8E79.70609@corvil.com \
--to=padraig.brady@corvil.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox