From: Rob Radez <rob@osinvestor.com>
To: Dave Jones <davej@codemonkey.org.uk>,
Wim Van Sebroeck <wim@iguana.be>, Rob Radez <rob@osinvestor.com>,
"Randy.Dunlap" <rddunlap@osdl.org>,
Russell King <rmk@arm.linux.org.uk>,
linux-kernel@vger.kernel.org
Cc: Matt_Domsch@dell.com
Subject: Re: Watchdog drivers
Date: Mon, 14 Oct 2002 11:11:47 -0400 [thread overview]
Message-ID: <20021014111147.Q16698@osinvestor.com> (raw)
In-Reply-To: <20021014130441.GA528@suse.de>; from davej@codemonkey.org.uk on Mon, Oct 14, 2002 at 02:04:41PM +0100
On Mon, Oct 14, 2002 at 02:04:41PM +0100, Dave Jones wrote:
> They remain character devices, so drivers/char/watchdog/ gets my vote.
> Any nay-sayers ?
I'm all in favor of drivers/char/watchdog/, but when I asked way back when,
I could never get a response from anyone upstream willing to take patches.
Also, I've got patches around from Matt Domsch that did the move, and changed
around the necessary drivers/char/ files. I haven't been keeping them up-to-
date, maybe Matt has.
Regards,
Rob Radez
next prev parent reply other threads:[~2002-10-14 15:06 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 [this message]
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
-- 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=20021014111147.Q16698@osinvestor.com \
--to=rob@osinvestor.com \
--cc=Matt_Domsch@dell.com \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=rmk@arm.linux.org.uk \
--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