From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] M68k wd33c93 locking
Date: Mon, 28 Jul 2003 10:49:00 +0200 [thread overview]
Message-ID: <20030728084859.GY7452@lug-owl.de> (raw)
In-Reply-To: <200307261451.h6QEpT9s002280@callisto.of.borg>
[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]
On Sat, 2003-07-26 16:51:29 +0200, Geert Uytterhoeven <geert@linux-m68k.org>
wrote in message <200307261451.h6QEpT9s002280@callisto.of.borg>:
> M68k wd33c93: host_lock is a pointer to a spinlock, not a spinlock (from Ralf
> Bächle)
> --- linux-2.6.x/drivers/scsi/a3000.c Fri May 9 10:21:34 2003
> +++ linux-m68k-2.6.x/drivers/scsi/a3000.c Fri Jun 6 13:33:13 2003
> @@ -36,9 +36,9 @@
> return IRQ_NONE;
> if (status & ISTR_INTS)
> {
> - spin_lock_irqsave(&a3000_host->host_lock, flags);
> + spin_lock_irqsave(a3000_host->host_lock, flags);
> wd33c93_intr (a3000_host);
> - spin_unlock_irqrestore(&a3000_host->host_lock, flags);
> + spin_unlock_irqrestore(a3000_host->host_lock, flags);
> return IRQ_HANDLED;
> }
> printk("Non-serviced A3000 SCSI-interrupt? ISTR = %02x\n", status);
Is this the fix to A3000 SCSI? Hmmm... I'd give my box another try these
days:)
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-28 8:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-26 14:51 [PATCH] M68k wd33c93 locking Geert Uytterhoeven
2003-07-28 8:49 ` Jan-Benedict Glaw [this message]
2003-07-30 20:59 ` Geert Uytterhoeven
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=20030728084859.GY7452@lug-owl.de \
--to=jbglaw@lug-owl.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).