mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Rob Radez <rob@osinvestor.com>
Cc: linux-kernel@vger.kernel.org,
	Marcelo Tosatti <marcelo@conectiva.com.br>,
	"David S. Miller" <davem@redhat.com>
Subject: Re: [RFC] Making drivers/char/watchdog
Date: Tue, 16 Apr 2002 12:56:45 +1000	[thread overview]
Message-ID: <12454.1018925805@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Mon, 15 Apr 2002 22:32:28 -0400." <Pine.LNX.4.33.0204152222100.17511-100000@pita.lan>

On Mon, 15 Apr 2002 22:32:28 -0400 (EDT), 
Rob Radez <rob@osinvestor.com> wrote:
>This e-mail probably doesn't affect 99% of you out there, but it's coming
>into your inboxes anyways :-).  How would people feel about moving the
>22 watchdog drivers into their own subdirectory off of drivers/char/ in
>both 2.4 and 2.5?  (Well, 2.5 only has 18 at the moment, but I'm planning
>on adding the 4 2.4-only drivers to 2.5 once updating 2.4 is done)
>
>I've received a bunch of inquiries about breaking them into their own
>subdirectory.  At the moment there are 20 watchdog drivers in
>drivers/char/ and 2 in drivers/sbus/char/ in 2.4, and 16 in drivers/char/
>and 2 in drivers/sbus/char/ in 2.5.  I think putting them all into one
>place will make them easier to maintain, more standardized, and less
>buggy.

Moving the watchdogs to their own directory makes sense, but watch out
for config sensitivity.  ATM drivers/sbus is only selected if the arch
is not m68k (anybody know why?) and the whole drivers/sbus/char
directory is conditioned on CONFIG_SBUSCHAR.


      reply	other threads:[~2002-04-16  2:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-16  2:32 Rob Radez
2002-04-16  2:56 ` Keith Owens [this message]

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=12454.1018925805@kao2.melbourne.sgi.com \
    --to=kaos@ocs.com.au \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=rob@osinvestor.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

all inboxes | Powered by JetHome®