public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@suse.de>
To: Russell King <rmk@arm.linux.org.uk>
Cc: "Adam J. Richter" <adam@yggdrasil.com>, 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:31:27 +0100	[thread overview]
Message-ID: <20020313153127.H7658@suse.de> (raw)
In-Reply-To: <200203122355.PAA08344@adam.yggdrasil.com> <20020313000229.D13558@flint.arm.linux.org.uk>
In-Reply-To: <20020313000229.D13558@flint.arm.linux.org.uk>; from rmk@arm.linux.org.uk on Wed, Mar 13, 2002 at 12:02:29AM +0000

On Wed, Mar 13, 2002 at 12:02:29AM +0000, Russell King wrote:
 > 
 > 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.

I pushed that revert to Linus. It was basically a cp of the driver
from the 2.4 tree to the current 2.5 one, diff and send. 
At least if someone now tries to "fix" it, it won't be lacking
any of the locking fixes that Alan did for 2.4.17

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

  reply	other threads:[~2002-03-13 14:31 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
2002-03-13 14:31   ` 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-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=20020313153127.H7658@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox