From: "David S. Miller" <davem@redhat.com>
To: geert@linux-m68k.org
Cc: alan@lxorguk.ukuu.org.uk, hch@infradead.org,
torvalds@transmeta.com, linux-kernel@vger.kernel.org,
dledford@redhat.com
Subject: Re: [PATCH] NCR53C9x ESP: C99 designated initializers
Date: Mon, 11 Nov 2002 01:43:28 -0800 (PST) [thread overview]
Message-ID: <20021111.014328.87369858.davem@redhat.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0211111029030.20946-100000@vervain.sonytel.be>
From: Geert Uytterhoeven <geert@linux-m68k.org>
Date: Mon, 11 Nov 2002 10:31:23 +0100 (MET)
[ Doug, you should just care about my eh_reset callback comments ]
On 10 Nov 2002, Alan Cox wrote:
> Reset is called with the lock held surely. How can the wait_event be
> right ?
I don't know. I just ported the Sun/SPARC ESP SCSI driver changes in 2.5.45 to
the NCR53C9x ESP SCSI drivers. If you're right, the same bug is present in
esp.c.
Dave?
That's a little inconvenient.
I have to wait for an interrupt from the chip to know the RESET
started by the eh_reset_bus_handler code is done, and I'm certainly
not going to spin there for 5 seconds or however long it decides to
take. :-)
Either eh_reset_bus_handler needs to be allowed to sleep, or it needs
to be changed so that an "RESET in progress, please wait" status can
be returned.
Doug?
BTW, what about merging esp.c and NCR53C9x.c?
I don't have the time to abstract away all of the various DMA portion
of the ESP chip handling to allow that. There are 12 different
combinations of ESP + DMA controller combinations on Sparc, so if you
do the changes you'll need to test that :-)
Franks a lot,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2002-11-11 9:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-03 10:46 [PATCH] NCR53C9x ESP: C99 designated initializers Geert Uytterhoeven
2002-11-03 13:13 ` Christoph Hellwig
2002-11-03 14:28 ` Geert Uytterhoeven
2002-11-03 14:33 ` Christoph Hellwig
2002-11-10 10:27 ` Geert Uytterhoeven
2002-11-10 14:38 ` Alan Cox
2002-11-11 9:31 ` Geert Uytterhoeven
2002-11-11 9:43 ` David S. Miller [this message]
2002-11-11 13:05 ` Alan Cox
2002-11-11 17:24 ` Linus Torvalds
2002-11-11 17:43 ` Arjan van de Ven
2002-11-11 20:31 ` Doug Ledford
2002-11-11 22:48 ` Alan Cox
2002-11-11 20:35 ` Doug Ledford
2002-11-11 21:01 ` Linus Torvalds
2002-11-11 21:24 ` Doug Ledford
-- strict thread matches above, loose matches on Subject: below --
2002-11-11 18:30 J.E.J. Bottomley
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=20021111.014328.87369858.davem@redhat.com \
--to=davem@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dledford@redhat.com \
--cc=geert@linux-m68k.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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