From: Christoph Hellwig <hch@infradead.org>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: gene.heskett@verizon.net, linux-scsi@vger.kernel.org
Subject: Re: advansys regions [Re: 2.4 vs 2.6 versions of include/linux/ioport.h]
Date: Thu, 7 Aug 2003 08:36:26 +0100 [thread overview]
Message-ID: <20030807083626.B766@infradead.org> (raw)
In-Reply-To: <20030806104041.4a09f4f0.rddunlap@osdl.org>; from rddunlap@osdl.org on Wed, Aug 06, 2003 at 10:40:41AM -0700
On Wed, Aug 06, 2003 at 10:40:41AM -0700, Randy.Dunlap wrote:
> I'm not terribly interested in spending much time on this driver,
> so the simplest thing to do IMO is to emulate check_region() with
> pairs of request_region() and release_region() calls. Yes, this
> is still racy, just like check_region() was. Is that a problem
> in your machine environment?
>
> Below is a patch that uses request_region/release_region pairs
> instead of check_region(). Does it work for you?
What the heck? Just continue using check_region if you don't want
to spend the time fixing it. At least we get a warning in that
case.
next prev parent reply other threads:[~2003-08-07 7:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 14:41 2.4 vs 2.6 versions of include/linux/ioport.h Gene Heskett
2003-08-05 14:57 ` Randy.Dunlap
2003-08-05 15:22 ` Gene Heskett
2003-08-05 15:45 ` Randy.Dunlap
2003-08-05 19:08 ` Gene Heskett
2003-08-05 22:07 ` 2.4 vs 2.6 ver# extra configure info CONFIGURE_ARGS += --disable-debug --enable-final --with-java=/usr/java/j2re1.4.1sions " Gene Heskett
2003-08-06 0:26 ` Andrew McGregor
2003-08-06 1:56 ` 2.4 vs 2.6 versions " Gene Heskett
2003-08-06 2:08 ` 2.5/2.6 NVidia (was Re: 2.4 vs 2.6 ver# Valdis.Kletnieks
2003-08-06 2:32 ` Gene Heskett
2003-08-06 2:53 ` Gene Heskett
2003-08-06 3:06 ` Valdis.Kletnieks
2003-08-06 5:51 ` 2.5/2.6 NVidia (was Re: 2.4 vs 2.6 version of ioport.h) Gene Heskett
2003-08-06 0:50 ` 2.4 vs 2.6 versions of include/linux/ioport.h Gene Heskett
2003-08-06 17:40 ` advansys regions [Re: 2.4 vs 2.6 versions of include/linux/ioport.h] Randy.Dunlap
2003-08-06 17:59 ` Matthew Wilcox
2003-08-06 18:02 ` Randy.Dunlap
2003-08-06 18:35 ` Gene Heskett
2003-08-06 18:50 ` Randy.Dunlap
2003-08-06 19:18 ` Gene Heskett
2003-08-06 23:20 ` Gene Heskett
2003-08-06 18:31 ` Gene Heskett
2003-08-07 7:36 ` Christoph Hellwig [this message]
2003-08-07 9:33 ` Gene Heskett
2003-08-07 9:47 ` Christoph Hellwig
2003-08-07 18:34 ` Gene Heskett
2003-08-07 18:42 ` Randy.Dunlap
2003-08-07 19:40 ` Gene Heskett
2003-08-05 15:10 ` 2.4 vs 2.6 versions of include/linux/ioport.h Gene Heskett
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=20030807083626.B766@infradead.org \
--to=hch@infradead.org \
--cc=gene.heskett@verizon.net \
--cc=linux-scsi@vger.kernel.org \
--cc=rddunlap@osdl.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 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.