From: Dave Jones <davej@codemonkey.org.uk>
To: Wim Van Sebroeck <wim@iguana.be>
Cc: Rob Radez <rob@osinvestor.com>,
"Randy.Dunlap" <rddunlap@osdl.org>,
Russell King <rmk@arm.linux.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: Watchdog drivers
Date: Mon, 14 Oct 2002 14:04:41 +0100 [thread overview]
Message-ID: <20021014130441.GA528@suse.de> (raw)
In-Reply-To: <20021014144158.A19209@medelec.uia.ac.be>
On Mon, Oct 14, 2002 at 02:41:58PM +0200, Wim Van Sebroeck wrote:
> On Mon, Oct 14, 2002 at 01:22:39PM +0100, Dave Jones wrote:
>
> > > Now I'm still left with my original question: wouldn't it be easier if we
> > > put all watchdog drivers in drivers/char/watchdog/ ?
> >
> > I'd say go for it. drivers/char/ is looking quite cluttered, and this
> > has the added advantage of decreasing the size of the Config.in and
> > config.help files too.
>
> I still see two options:
> 1) drivers/char/watchdog/
> 2) drivers/watchdog/
>
> Not sure what's best in this case...
They remain character devices, so drivers/char/watchdog/ gets my vote.
Any nay-sayers ?
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
next prev parent reply other threads:[~2002-10-14 12:57 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 [this message]
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
-- 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=20021014130441.GA528@suse.de \
--to=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=rmk@arm.linux.org.uk \
--cc=rob@osinvestor.com \
--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