From: "Stephen Biggs" <yrgrknmxpzlk@gawab.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [PATCH] Reduction of compile warnings (Warning: long post
Date: Sun, 13 Feb 2005 18:57:24 +0000 [thread overview]
Message-ID: <420FBF34.27097.150F1D@localhost> (raw)
In-Reply-To: <420953CC.2707.A99E9B@localhost>
[-- Attachment #1: Mail message body --]
[-- Type: text/plain, Size: 810 bytes --]
On 11 Feb 2005 at 13:51, Christoph Hellwig wrote:
> On Fri, Feb 11, 2005 at 02:45:20PM +0100, walter harms wrote:
> > void __iomem *)ioaddr->feature_addr);
>
> this bit looks very wrong. What type is ioaddr->feature_addr? It really
> should be a pointer to <whatever> __iomem and not cast would be needed.
>
>
It is declared as "unsigned long". If you do a findall and grep for
feature_addr, you will find that it is used in a lot of math before being
stored.
So, if you change the declarations of this and the other *_addr structure
elements to "volatile void __iomem *" then casting would need to be done
on them in the arithmetic statements, which makes less sense because
arithmetic is being done on "void *".
It's 6 of one, half a dozen of the other. IMHO, my solution is a bit
cleaner.
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
prev parent reply other threads:[~2005-02-13 18:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 22:05 [KJ] [PATCH] Reduction of compile warnings (Warning: long post Stephen Biggs
2005-02-08 23:43 ` Jim Nelson
2005-02-09 7:29 ` Stephen Biggs
2005-02-09 8:22 ` Christophe Lucas
2005-02-09 10:43 ` Jim Nelson
2005-02-09 19:41 ` Stephen Biggs
2005-02-11 0:59 ` Randy.Dunlap
2005-02-11 13:45 ` walter harms
2005-02-11 13:51 ` Christoph Hellwig
2005-02-11 14:51 ` walter harms
2005-02-13 18:57 ` Stephen Biggs [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=420FBF34.27097.150F1D@localhost \
--to=yrgrknmxpzlk@gawab.com \
--cc=kernel-janitors@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 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.