mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: adam@yggdrasil.com (Adam J. Richter)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Big patch: linux-2.5.2-pre11/drivers/scsi compilation fixes
Date: Fri, 11 Jan 2002 14:42:03 +0000 (GMT)	[thread overview]
Message-ID: <E16P2sd-0007pd-00@the-village.bc.nu> (raw)
In-Reply-To: <20020111051456.A12788@baldur.yggdrasil.com> from "Adam J. Richter" at Jan 11, 2002 05:14:56 AM

> +	if (!atomic_dec_and_test(&main_running)) {
>  		NCR5380_main();

This change is not required

>  /* Run the coroutine if it isn't already running. */
> +	spin_unlock_irq(&instance->host_lock);
>  	run_main();
> +	spin_lock_irq(&instance->host_lock);

This hangs the machine recursively re-entering under load.


I specifically told people not to hack on the old NCR5380 driver. You've 
taken a semi broken driver, destroyed it completely and risked disk corruption
for anyone who uses it.

What really annoys me is that I've already asked you specifically not to
submit patches to that driver but to take the 2.4.18pre version of the
driver and port that one forward if you must fiddle with it. Instead you've
wasted your time, and tried to make the future merge harder.

Its absolutely obvious from the changes that you have no grasp how the
locking in that driver is handled, nor what it depends upon. If you had 
understood that locking you'd have realised you were hacking on a driver 
version that was totally flawed.

How many other maintainers have you ignored trying to send in untested
patches to their drivers ?

Alan

  parent reply	other threads:[~2002-01-11 14:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-11 13:14 Adam J. Richter
2002-01-11 13:18 ` Jens Axboe
2002-01-11 13:45   ` Martin Dalecki
2002-01-11 14:20     ` Alan Cox
2002-01-11 14:42 ` Alan Cox [this message]
2002-01-11 16:59 Adam J. Richter
2002-01-11 17:27 ` 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=E16P2sd-0007pd-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=adam@yggdrasil.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®