From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: nick.cheng@areca.com.tw
Cc: 'Andrew Morton' <akpm@linux-foundation.org>,
linux-scsi@vger.kernel.org, randy.dunlap@oracle.com,
'Tomas Henzl' <thenzl@redhat.com>,
viro@ftp.linux.org.uk
Subject: Re: [PATCH] modify the type of element of MessageUnit_B in arcmsr
Date: Tue, 04 Mar 2008 10:39:47 -0600 [thread overview]
Message-ID: <1204648787.3091.25.camel@localhost.localdomain> (raw)
In-Reply-To: <005e01c87ddd$1c22db70$8800a8c0@Nick>
On Tue, 2008-03-04 at 17:49 +0800, nickcheng wrote:
> Subject: [PATCH] scsi: modify the element type of MessageUnit_B in
> arcmsr-1.20.00.15-80227
> From: Nick Cheng <nick.cheng@areca.com.tw>
> Description:
> *** modify the element type of MessageUnit_B in arcmsr-1.20.00.15-80227 to
> keep off the error while doing iounmap in arcmsr_free_ccb_pool()
What's the actual error this causes?
Looking at the code, all of these registers are genuinely 32 bits long,
so having them defined as uint32_t __iomem * is fine; so is having them
defined as void __iomem *, because void * can be transparently cast to
any pointer.
Because the readX/writeX routines are prototyped in terms of void
__iomem *, they do the casting transparently (and without warning), so
there's no useful typechecking with the uint32_t __iomem * definition,
thus I only have a tiny marginal preference for labelling the registers
with their correct width. But I would like to understand what the error
is you're seeing.
Thanks,
James
next prev parent reply other threads:[~2008-03-04 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 9:49 [PATCH] modify the type of element of MessageUnit_B in arcmsr nickcheng
2008-03-04 16:39 ` James Bottomley [this message]
2008-03-05 7:38 ` nickcheng
2008-03-05 15:30 ` James Bottomley
2008-03-06 2:04 ` nickcheng
2008-03-06 22:28 ` James Bottomley
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=1204648787.3091.25.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nick.cheng@areca.com.tw \
--cc=randy.dunlap@oracle.com \
--cc=thenzl@redhat.com \
--cc=viro@ftp.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