public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J . A . Magallon" <jamagallon@able.es>
To: "Justin T . Gibbs" <gibbs@scsiguy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: aic7xxx (and sym53c8xx) plans
Date: Thu, 15 Feb 2001 21:20:07 +0100	[thread overview]
Message-ID: <20010215212007.A995@werewolf.able.es> (raw)
In-Reply-To: <85F1402515F13F498EE9FBBC5E07594220AD85@TTGCS.teamtoolz.net> <200102151747.f1FHlDO64938@aslan.scsiguy.com>
In-Reply-To: <200102151747.f1FHlDO64938@aslan.scsiguy.com>; from gibbs@scsiguy.com on Thu, Feb 15, 2001 at 18:47:13 +0100


On 02.15 Justin T. Gibbs wrote:
> >All of my boxes with that card are on 2.2.16. The rest are on 2.4.1, so I
> >don't really have a need to test 2.2.18 as I would rather be on 2.4.x for
> >all of my boxes.
> 
> Well, I'll try and generate patches against 2.2.16 soon.  I probably
> need to support 2.2.14 too.  There are already so many versions to
> keep track of, the sooner the driver becomes embedded, the better.
> 

Please, I think it would be much more useful a patch against the latest
2.2.19-pre (if that one for 2.2.18 does not work, I have not tried)
and the latest 2.4.1-ac14, that is what people experiments with.

People who has still a 2.2.14 or 16 looks like does not worry too much
about updating and building kernels, and it they go into the work, they
can just go to 2.2.18, compatible with 16 and 14 and much more stable.

I think it is better to work for preX kernels than for eldely ones.

-- 
J.A. Magallon                                                      $> cd pub
mailto:jamagallon@able.es                                          $> more beer

Linux werewolf 2.4.1-ac14 #1 SMP Thu Feb 15 16:05:52 CET 2001 i686


  reply	other threads:[~2001-02-15 20:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-15 17:38 aic7xxx (and sym53c8xx) plans Matt Liotta
2001-02-15 17:47 ` Justin T. Gibbs
2001-02-15 20:20   ` J . A . Magallon [this message]
2001-02-15 20:28     ` Chip Salzenberg
2001-02-15 23:42       ` J . A . Magallon
  -- strict thread matches above, loose matches on Subject: below --
2001-02-19 15:28 Nathan Black
2001-02-15 17:30 Matt Liotta
2001-02-15 17:35 ` Justin T. Gibbs
2001-02-15 17:19 Nathan Black
2001-02-18  0:05 ` Peter Samuelson
2001-02-18 17:14   ` Justin T. Gibbs
2001-02-19 20:27     ` Peter Samuelson
2001-02-19 19:32       ` Gérard Roudier
2001-02-19 21:39         ` Matthew Jacob
2001-02-19 21:58       ` Justin T. Gibbs
2001-02-15  2:03 aic7xxx plans Wakko Warner
2001-02-15  2:06 ` Matthew Jacob
2001-02-15  2:20   ` aic7xxx (and sym53c8xx) plans Chip Salzenberg
2001-02-15  2:28     ` Matthew Jacob
2001-02-15 11:45       ` Alan Cox

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=20010215212007.A995@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=gibbs@scsiguy.com \
    --cc=linux-kernel@vger.kernel.org \
    /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