All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [BK] Move watchdog drivers to drivers/char/watchdog/
Date: Fri, 22 Nov 2002 12:09:21 +0000	[thread overview]
Message-ID: <20021122120921.GA17439@suse.de> (raw)

Someone suggested moving the dozen or so watchdog drivers we
have in drivers/char/ to their own dir in drivers/char/watchdog
a few weeks ago. Then nothing happened, so I got bored waiting
and did it myself.

No code changes, just moving files around.

For the bk-impaired/agnostic, the (large) GNU diff from this is at 
ftp.kernel.org/pub/linux/kernel/people/davej/patches/2.5/2.5.48/move-watchdogs.diff.gz

Pull from bk://linux-dj.bkbits.net/watchdog

		Dave

diffstat:
 Kconfig                 |  284 --------------------
 Makefile                |   23 -
 acquirewdt.c            |  251 -----------------
 advantechwdt.c          |  280 --------------------
 eurotechwdt.c           |  501 -----------------------------------
 i810-tco.c              |  431 ------------------------------
 ib700wdt.c              |  311 ----------------------
 machzwd.c               |  557 ---------------------------------------
 mixcomwd.c              |  282 --------------------
 pcwd.c                  |  672 ------------------------------------------------
 sbc60xxwdt.c            |  354 -------------------------
 scx200_wdt.c            |  277 -------------------
 shwdt.c                 |  417 -----------------------------
 softdog.c               |  196 --------------
 w83877f_wdt.c           |  366 --------------------------
 watchdog/Kconfig        |  286 ++++++++++++++++++++
 watchdog/Makefile       |   27 +
 watchdog/acquirewdt.c   |  251 +++++++++++++++++
 watchdog/advantechwdt.c |  280 ++++++++++++++++++++
 watchdog/eurotechwdt.c  |  501 +++++++++++++++++++++++++++++++++++
 watchdog/i810-tco.c     |  431 ++++++++++++++++++++++++++++++
 watchdog/i810-tco.h     |   42 +++
 watchdog/ib700wdt.c     |  311 ++++++++++++++++++++++
 watchdog/machzwd.c      |  557 +++++++++++++++++++++++++++++++++++++++
 watchdog/mixcomwd.c     |  282 ++++++++++++++++++++
 watchdog/pcwd.c         |  672 ++++++++++++++++++++++++++++++++++++++++++++++++
 watchdog/sbc60xxwdt.c   |  354 +++++++++++++++++++++++++
 watchdog/scx200_wdt.c   |  277 +++++++++++++++++++
 watchdog/shwdt.c        |  417 +++++++++++++++++++++++++++++
 watchdog/softdog.c      |  196 ++++++++++++++
 watchdog/w83877f_wdt.c  |  366 ++++++++++++++++++++++++++
 watchdog/wd501p.h       |   91 ++++++
 watchdog/wdt.c          |  565 ++++++++++++++++++++++++++++++++++++++++
 watchdog/wdt285.c       |  193 +++++++++++++
 watchdog/wdt977.c       |  346 ++++++++++++++++++++++++
 watchdog/wdt_pci.c      |  653 ++++++++++++++++++++++++++++++++++++++++++++++
 wd501p.h                |   91 ------
 wdt.c                   |  565 ----------------------------------------
 wdt285.c                |  193 -------------
 wdt977.c                |  346 ------------------------
 wdt_pci.c               |  653 ----------------------------------------------

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

                 reply	other threads:[~2002-11-22 12:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20021122120921.GA17439@suse.de \
    --to=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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.