public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Skip Ford <skip.ford@verizon.net>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Make ide-scsi compile in 2.5
Date: Sun, 27 Jan 2002 10:51:17 -0500	[thread overview]
Message-ID: <20020127105117.A571@s> (raw)
In-Reply-To: <20020127024631.A28936@wotan.suse.de>
In-Reply-To: <20020127024631.A28936@wotan.suse.de>; from ak@suse.de on Sun, Jan 27, 2002 at 02:46:31AM +0100

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Andi Kleen wrote:
> 
> ide-scsi doesn't compile currently in 2.5.x. This patch fixes it in a 
> rather hackish way by adding some kmap_atomic()s.  It would be 
> probably better to kmap earlier in process context in the request 
> function instead, but I leave this to the people who know more 
> about IDE/block layer than me (but apparently not compile ide-scsi..)
> I'm also not totally convinced that it is deadlock free here to use
> KM_BOUNCE_READ here, it may be safer to add a new bounce type. 
> You have been warned. 
> 
> I have only tested it without highmem and it works for me. 
> 
> Hopefully there will be eventually a better fix, but for now it 
> allows to burn (and mount if you use /dev/scd* for ide) CDs under 2.5 again. 

There was a brief period when 2.5 was released and changes went in that
it didn't compile.  Then that was fixed, but it couldn't mount or burn,
but that was also fixed.

I burned a CD a few days ago and it worked fine.  Maybe you have a
partial patch hanging around or something.

- -- 
Skip  ID: 0x7EDDDB0A
-----BEGIN PGP SIGNATURE-----

iEYEARECAAYFAjxUIewACgkQBMKxVH7d2wrDwACgrG0Nidkkl1uw6pSu33+NKxFR
9lwAnREktZYiYo2sKTSL4kpWLSnRK4BY
=43xD
-----END PGP SIGNATURE-----

      parent reply	other threads:[~2002-01-27 15:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-27  1:46 [PATCH] Make ide-scsi compile in 2.5 Andi Kleen
2002-01-27 10:49 ` Jens Axboe
2002-01-27 15:51 ` Skip Ford [this message]

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=20020127105117.A571@s \
    --to=skip.ford@verizon.net \
    --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