mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: davidsen@tmr.com (Bill Davidsen)
Cc: haveblue@us.ibm.com (Dave Hansen),
	alan@lxorguk.ukuu.org.uk (Alan Cox),
	linux-kernel@vger.kernel.org (Linux Kernel Mailing List)
Subject: Re: [PATCH] fix ips driver compile problems
Date: Tue, 16 Apr 2002 20:12:10 +0100 (BST)	[thread overview]
Message-ID: <E16xYN8-0000dv-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.LNX.3.96.1020416143110.27884A-100000@gatekeeper.tmr.com> from "Bill Davidsen" at Apr 16, 2002 02:47:45 PM

>   Let's clarify. Is there a policy to get rid of drivers which don't
> conform, and if so are all the other drivers claimed to be compliant and
> this the only one which isn't? And if so, why hasn't someone just

They need fixing not removing. But right at the moment trying to fix drivers
is a fairly painful business since th block and scsi layers are still 
somewhat in flux. Also for some drivers bringing them up to the 2.5 
world is non trivial (eg I2O) and takes time anyway.

> Otherwise:
> - this makes the driver compile - good
> - this patch makes the driver WORK - also good

Bad.. - because now when you come to check you have them all fixed you'll
miss it out, and bad stuff might occur. You want it to choke unless the
user said "please dont choke on..." just so you can find them.

DaveJ's patch is much nicer

Alan


  reply	other threads:[~2002-04-16 18:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-16 15:05 Dave Hansen
2002-04-16 16:01 ` Alan Cox
2002-04-16 16:11   ` Dave Hansen
2002-04-16 18:09     ` Alan Cox
2002-04-16 18:47     ` Bill Davidsen
2002-04-16 19:12       ` Alan Cox [this message]
2002-04-16 17:49 ` David S. Miller
2002-04-16 18:03   ` Linus Torvalds
2002-04-16 18:30     ` Alan Cox
2002-04-16 18:26       ` Dave Jones
2002-04-16 18:59       ` Linus Torvalds

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=E16xYN8-0000dv-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=davidsen@tmr.com \
    --cc=haveblue@us.ibm.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

all inboxes | Powered by JetHome®