From: Dave Jones <davej@suse.de>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: rmk@arm.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: linux-2.5.6 scsi DMA mapping and compilation fixes (not yet working)
Date: Wed, 13 Mar 2002 15:33:27 +0100 [thread overview]
Message-ID: <20020313153327.I7658@suse.de> (raw)
In-Reply-To: <200203130023.QAA08389@adam.yggdrasil.com>
In-Reply-To: <200203130023.QAA08389@adam.yggdrasil.com>; from adam@yggdrasil.com on Tue, Mar 12, 2002 at 04:23:24PM -0800
On Tue, Mar 12, 2002 at 04:23:24PM -0800, Adam J. Richter wrote:
> Maybe you are thinking of the patches that I posted a
> while ago that included an update to some locking changes for
> a bunch of the scsi drivers. Alan spoke up and said that
> I should not apply the NCR53C80 part of those patches because
> I had made a mistake and becuase there was a newer driver in 2.4,
Someone else did exactly the same thing you did, and somehow
Linus picked it up that time. Anyway, its backed out now,
so its a moot point.
> Maybe you were thinking of some other event when you
> said "I believe changes to NCR53c80 were recently reverted back because
> these 'fixes' lead to massive data corruption." If so, I would be
> interested in hearing about it.
The data corruption issue was the lack of fixed locking and
assorted fixes that Alan did after the 2.4/2.5 split.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-03-13 14:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 0:23 linux-2.5.6 scsi DMA mapping and compilation fixes (not yet working) Adam J. Richter
2002-03-13 14:33 ` Dave Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-14 1:02 Adam J. Richter
2002-03-14 1:27 ` Alan Cox
2002-03-13 17:17 Adam J. Richter
2002-03-13 17:38 ` Alan Cox
2002-03-13 15:51 Adam J. Richter
2002-03-13 16:22 ` Alan Cox
2002-03-12 23:55 Adam J. Richter
2002-03-13 0:02 ` Russell King
2002-03-13 14:31 ` Dave Jones
2002-03-12 20:56 Adam J. Richter
2002-03-12 23:42 ` Russell King
2002-03-13 16:51 ` 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=20020313153327.I7658@suse.de \
--to=davej@suse.de \
--cc=adam@yggdrasil.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.