All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Lynch <rusty@linux.co.intel.com>
To: Patrick Mochel <mochel@osdl.org>
Cc: Dave Jones <davej@codemonkey.org.uk>,
	wingel@nano-systems.com, lkml <linux-kernel@vger.kernel.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH][RFC] Proposal for a new watchdog interface using sysfs
Date: 13 Feb 2003 07:51:45 -0800	[thread overview]
Message-ID: <1045151506.1189.1.camel@vmhack> (raw)
In-Reply-To: <Pine.LNX.4.33.0302131002420.1133-100000@localhost.localdomain>

On Thu, 2003-02-13 at 08:04, Patrick Mochel wrote:
> 
> On 13 Feb 2003, Rusty Lynch wrote:
> 
> > On Thu, 2003-02-13 at 03:55, Dave Jones wrote:
> > > On Wed, Feb 12, 2003 at 07:16:55PM -0800, Rusty Lynch wrote:
> > >  > Basically, with the help of some watchdog infrastructure code, we could make 
> > >  > each watchdog device register as a platform_device named watchdog, so for 
> > >  > every watchdog on the system there is a /sys/devices/legacy/watchdogN/ 
> > >  > directory created for it.  
> > > 
> > > Why legacy ? That seems an odd place to be putting these.
> > > 
> > > 		Dave
> > > 
> > > -- 
> > > | Dave Jones.        http://www.codemonkey.org.uk
> > > | SuSE Labs
> > 
> > The watchdogN devices show up under the "legacy" directory because
> > they are platform devices.  From reading the driver-model documentation,
> > I believe that platform devices are the correct way of categorizing
> > watchdog devices.
> > 
> > <pasting from Documentation/driver-model/platform.txt>
> > 
> > Platform devices
> > ~~~~~~~~~~~~~~~~
> 
> You could regard them as 'system' devices, and have them show up in 
> devices/sys/, which would make more sense than 'legacy'.
> 
> 	-pat

Ok, system device is the winner.

    -rustyl


  reply	other threads:[~2003-02-13 16:30 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 [this message]
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
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=1045151506.1189.1.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=wingel@nano-systems.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 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.