linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Mikael Pettersson <mikpe@csd.uu.se>,
	heine@instmath.rwth-aachen.de, alan@lxorguk.ukuu.org.uk,
	linux-kernel@vger.kernel.org
Subject: Re: time for some drivers to be removed?
Date: Tue, 5 Aug 2003 15:35:10 +0200	[thread overview]
Message-ID: <16175.45710.993756.301205@gargle.gargle.HOWL> (raw)
In-Reply-To: <20030805130324.GC16091@fs.tum.de>

Adrian Bunk writes:
 > On Tue, Aug 05, 2003 at 02:42:28PM +0200, Mikael Pettersson wrote:
 > > On 27 Jul 2003 21:56:11 +0100, Alan Cox wrote:
 > > > On Sul, 2003-07-27 at 21:56, Adrian Bunk wrote:
 > > > > That's no problem for me.
 > > > > 
 > > > > The only question is how to call the option that allows building only on
 > > > > UP (e.g. cli/sti usage in the driver)? My suggestion was BROKEN_ON_SMP,
 > > > > would you suggest OBSOLETE_ON_SMP?
 > > > 
 > > > Interesting question - whatever I guess. We don't have an existing convention.
 > > > How many drivers have we got nowdays that failing on just SMP ?
 > > 
 > > ftape fails on SMP due to sti/save_flags/restore_flags removal.
 > >...
 > > I have the HW so I can test patches if someone feels like fixing this.
 > 
 > There seems to be an upgrade f the ftape code available at [1], but I 
 > haven't investigated on the status or plans to integrate it into 2.6.

ftape-4.04? That's been a non-integrated external package for ages and ages.
I doubt there's been any updates in it for 2.5/2.6 kernels.

I used to use ftape-4 snapshots in late 2.1 and most 2.2 kernels, but patch
maintenance overhead made me go back to the kernel's ftape before 2.4.0.

Given how few still use these antiques (my "fast" Conner/Seagate drive gives
150KBps backup speed, wow!) I think simply maintaining status quo is the most
reasonable use of peoples' time.

  reply	other threads:[~2003-08-05 13:35 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-05 12:42 time for some drivers to be removed? Mikael Pettersson
2003-08-05 13:03 ` Adrian Bunk
2003-08-05 13:35   ` Mikael Pettersson [this message]
2003-08-05 13:48     ` Adrian Bunk
2003-08-05 14:01       ` Mikael Pettersson
2003-08-06 10:06         ` Claus-Justus Heine
2003-08-09 19:40           ` Adrian Bunk
2003-08-05 16:35 ` Alan Cox
2003-08-05 18:47   ` Leopold Gouverneur
  -- strict thread matches above, loose matches on Subject: below --
2003-08-14  5:34 John Bradford
2003-08-13 20:55 John Bradford
2003-08-13 20:50 ` Adrian Bunk
2003-08-13 20:55 ` Bill Davidsen
2003-07-28  7:12 linux
2003-07-27 16:22 John Bradford
2003-07-25 11:10 John Bradford
2003-07-24 18:29 John Bradford
2003-07-24 18:31 ` Robert P. J. Day
2003-07-24 19:31   ` Eli Carter
2003-07-25 10:48 ` Bas Mevissen
2003-07-24 14:43 John Bradford
2003-07-24 19:24 ` Brian Jackson
2003-07-24 12:20 Robert P. J. Day
2003-07-24 14:58 ` Alan Cox
2003-07-24 15:34   ` Bas Mevissen
2003-07-24 17:32     ` Diego Calleja García
2003-07-24 17:50       ` Robert P. J. Day
2003-07-24 19:16         ` Diego Calleja García
2003-07-24 19:43           ` Robert P. J. Day
2003-07-24 18:02       ` Samuel Flory
2003-07-24 19:07     ` Alan Cox
2003-07-25 10:48       ` Bas Mevissen
2003-07-27 15:31 ` Adrian Bunk
2003-07-27 15:59   ` David D. Hagood
2003-07-27 16:18     ` Adrian Bunk
2003-07-27 16:40     ` Alan Cox
2003-07-27 17:00       ` Adrian Bunk
2003-07-27 18:45       ` David D. Hagood
2003-07-27 20:40         ` Alan Cox
2003-07-27 20:56           ` Adrian Bunk
2003-07-27 20:56             ` Alan Cox
2003-07-28  2:23               ` Herbert Pötzl
2003-07-29 19:33               ` Adrian Bunk
2003-08-13 20:16                 ` Bill Davidsen
2003-08-09 18:04   ` David Woodhouse
2003-08-09 19:36     ` Adrian Bunk

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=16175.45710.993756.301205@gargle.gargle.HOWL \
    --to=mikpe@csd.uu.se \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bunk@fs.tum.de \
    --cc=heine@instmath.rwth-aachen.de \
    --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;
as well as URLs for NNTP newsgroup(s).