From: Rusty Lynch <rusty@linux.co.intel.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Matt Porter <porter@cox.net>,
Scott Murray <scottm@somanetworks.com>,
Patrick Mochel <mochel@osdl.org>,
Dave Jones <davej@codemonkey.org.uk>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][RFC] Proposal for a new watchdog interface using sysfs
Date: 14 Feb 2003 07:32:33 -0800 [thread overview]
Message-ID: <1045236757.12974.14.camel@vmhack> (raw)
In-Reply-To: <1045234137.7958.17.camel@irongate.swansea.linux.org.uk>
On Fri, 2003-02-14 at 06:48, Alan Cox wrote:
> On Fri, 2003-02-14 at 00:47, Rusty Lynch wrote:
> > Ok, I had to go and read the driver-model documentation a couple of more
> > times, but after I actually started writing some code it finally started
> > to make sense.
>
> The watchdog_ops is probably a good thing anyway. If you also use that
> same structure with the base watchdog module having the ioctl parser all
> the ioctl handling funnies and quirks in the drivers go away except
> for driver private stuff.
>
> Two for the price of one
>
> Alan
>
Since only one driver can register as the /dev/watchdog (ie
major=10/minor=130 char device), would it be better if:
* the first watchdog driver to register with the base also gets
registered as the watchdog misc device, and when that driver unregisters
then the second watchdog to register now gets registered as the misc
device, etc.
* each watchdog driver gets an additional sysfs file named 'misc', where
writing a '1' to the file causes the driver to become the registered
misc watchdog device.
* something else
--rustyl
next prev parent reply other threads:[~2003-02-14 16:34 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 3:16 [PATCH][RFC] Proposal for a new watchdog interface using sysfs Rusty Lynch
2003-02-13 4:27 ` Daniel Pittman
2003-02-13 7:32 ` Rusty Lynch
2003-02-13 11:55 ` Dave Jones
2003-02-13 15:34 ` Rusty Lynch
2003-02-13 16:04 ` Patrick Mochel
2003-02-13 15:51 ` Rusty Lynch
2003-02-13 19:07 ` Dave Jones
2003-02-13 18:31 ` Rusty Lynch
2003-02-13 19:19 ` Patrick Mochel
2003-02-13 21:12 ` Scott Murray
2003-02-13 22:58 ` Matt Porter
2003-02-13 22:05 ` Rusty Lynch
2003-02-14 0:47 ` Rusty Lynch
2003-02-14 14:48 ` Alan Cox
2003-02-14 15:32 ` Rusty Lynch [this message]
2003-02-14 17:55 ` Alan Cox
2003-02-14 19:02 ` Rusty Lynch
2003-02-14 20:43 ` Alan Cox
2003-02-14 21:12 ` Joel Becker
2003-02-14 13:48 ` Valdis.Kletnieks
2003-02-14 14:57 ` Alan Cox
2003-02-13 16:04 ` Dave Jones
2003-02-13 18:20 ` Rusty Lynch
2003-02-13 18:21 ` Rusty Lynch
2003-02-13 23:04 ` Pavel Machek
2003-02-14 22:12 ` Alan Cox
2003-02-14 21:35 ` Pavel Machek
2003-02-14 23:17 ` Rusty Lynch
2003-02-15 1:54 ` Alan Cox
2003-02-15 8:27 ` Cort Dougan
2003-02-15 9:13 ` John Bradford
2003-02-15 21:03 ` Alan Cox
2003-02-15 20:37 ` John Bradford
2003-02-15 12:42 ` Ingo Oeser
2003-02-15 17:26 ` Pavel Machek
2003-02-19 5:24 ` Rusty Lynch
2003-02-20 21:19 ` Jakob Oestergaard
2003-02-20 22:36 ` Alan Cox
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=1045236757.12974.14.camel@vmhack \
--to=rusty@linux.co.intel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=porter@cox.net \
--cc=scottm@somanetworks.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