[RFC] Making drivers/char/watchdog

[RFC] Making drivers/char/watchdog

[Rob Radez]

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.

Regards,
Rob Radez

Re: [RFC] Making drivers/char/watchdog

[Keith Owens]

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.