From: Matt_Domsch@Dell.com
To: rob@osinvestor.com, davej@codemonkey.org.uk, wim@iguana.be,
rddunlap@osdl.org, rmk@arm.linux.org.uk,
linux-kernel@vger.kernel.org
Subject: RE: Watchdog drivers
Date: Mon, 14 Oct 2002 10:51:59 -0500 [thread overview]
Message-ID: <20BF5713E14D5B48AA289F72BD372D68C1E9A1@AUSXMPC122.aus.amer.dell.com> (raw)
> Also, I've got patches around from Matt Domsch that did the
> move, and changed
> around the necessary drivers/char/ files. I haven't been
> keeping them up-to- date, maybe Matt has.
I haven't been, but it doesn't look too painful to do it. The Natsemi
SCx200 merge is what's screwing up BK's automerge of it (I hadn't updated
that tree since April...).
The move work took me a few hours last time I did it, I can resurrect that
now that there's interest. Give me a few hours, today's kind of busy...
Thanks,
Matt
--
Matt Domsch
Sr. Software Engineer, Lead Engineer, Architect
Dell Linux Solutions www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
next reply other threads:[~2002-10-14 15:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-14 15:51 Matt_Domsch [this message]
2002-10-14 16:40 ` Watchdog drivers 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
-- strict thread matches above, loose matches on Subject: below --
2002-10-15 12:57 Matt_Domsch
2002-10-13 17:40 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
2002-10-14 15:11 ` Rob Radez
2002-10-14 15:58 ` Randy.Dunlap
2002-10-15 9:35 ` David Woodhouse
2002-10-15 11:20 ` Dave Jones
2002-10-14 9:29 ` Padraig Brady
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=20BF5713E14D5B48AA289F72BD372D68C1E9A1@AUSXMPC122.aus.amer.dell.com \
--to=matt_domsch@dell.com \
--cc=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;
as well as URLs for NNTP newsgroup(s).