linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tom Sightler" <ttsig@tuxyturvy.com>
To: "Zach Brown" <zab@zabbo.net>, <linux-kernel@vger.kernel.org>
Subject: Re: [CFT] maestro update vs 2.2.18
Date: Sun, 4 Mar 2001 20:44:55 -0500	[thread overview]
Message-ID: <002401c0a515$e7998c70$1601a8c0@zeusinc.com> (raw)
In-Reply-To: <20010304183017.A19760@tetsuo.zabbo.net>

> Its an awfully large diff, so it can be fetched from:
>
> http://www.zabbo.net/maestro/patches/2.2.18-mega-1.diff.gz
>
> if this works I'll officially submit it and make the same sorts of
> changes to 2.4.

I'd love to test this on my Dell 5000e (Maestro 2E) but it's pretty
impractical for me to return to the 2.2.x kernels.  I know you said you'll
wait before making the changes to 2.4, but I think you'll get more testers
if you turn it out sooner rather than later.

Later,
Tom



      reply	other threads:[~2001-03-05  1:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-04 23:30 [CFT] maestro update vs 2.2.18 Zach Brown
2001-03-05  1:44 ` Tom Sightler [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='002401c0a515$e7998c70$1601a8c0@zeusinc.com' \
    --to=ttsig@tuxyturvy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zab@zabbo.net \
    /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).