Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 14 Oct 2002 11:54:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 14 Oct 2002 11:54:16 -0400 Received: from air-2.osdl.org ([65.172.181.6]:31106 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id ; Mon, 14 Oct 2002 11:54:15 -0400 Date: Mon, 14 Oct 2002 08:58:02 -0700 (PDT) From: "Randy.Dunlap" X-X-Sender: To: Wim Van Sebroeck cc: Dave Jones , Rob Radez , Russell King , Subject: Re: Watchdog drivers In-Reply-To: <20021014144158.A19209@medelec.uia.ac.be> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1034 Lines: 30 On Mon, 14 Oct 2002, 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... I agree that you should split them out. I would expect them to be in drivers/char/watchdog . -- ~Randy "In general, avoiding problems is better than solving them." -- from "#ifdef Considered Harmful", Spencer & Collyer, USENIX 1992. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/