From: Russell King <rmk@arm.linux.org.uk>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: 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 00:02:29 +0000 [thread overview]
Message-ID: <20020313000229.D13558@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200203122355.PAA08344@adam.yggdrasil.com>
In-Reply-To: <200203122355.PAA08344@adam.yggdrasil.com>; from adam@yggdrasil.com on Tue, Mar 12, 2002 at 03:55:36PM -0800
On Tue, Mar 12, 2002 at 03:55:36PM -0800, Adam J. Richter wrote:
> Are you talking about an event that occurred in the 2.4
> tree or the 2.5 tree? Are you saying that the newer driver in
> 2.4 was reverted back to the older driver (i.e., the one that
> is in 2.5), or are you saying that someone made some attempt
> at porting the 2.5 tree's NCR53C80 driver the new DMA mapping
> interface and then backed them out?
Someone had a go at "making 2.5 compile" without taking Alan's 2.4
changes. It went into Linus tree. It got subsequently reverted
because of the reasons I outlined in my previous mail.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-03-13 0:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-12 23:55 linux-2.5.6 scsi DMA mapping and compilation fixes (not yet working) Adam J. Richter
2002-03-13 0:02 ` Russell King [this message]
2002-03-13 14:31 ` Dave Jones
-- 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-13 0:23 Adam J. Richter
2002-03-13 14:33 ` 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=20020313000229.D13558@flint.arm.linux.org.uk \
--to=rmk@arm.linux.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