linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: kurt.van.dijck@eia.be (Kurt Van Dijck)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/7] mfd: add pruss mfd driver.
Date: Thu, 24 Mar 2011 14:41:42 +0100	[thread overview]
Message-ID: <20110324134142.GB27124@e-circ.dyndns.org> (raw)
In-Reply-To: <4D8B4623.4010709@pengutronix.de>

On Thu, Mar 24, 2011 at 02:24:51PM +0100, Marc Kleine-Budde wrote:
> On 03/24/2011 02:16 PM, Subhasish Ghosh wrote:
> > Hello,
> > 
> > With make C=1 I am receiving some warnings such as:
> > 
> > warning: cast removes address space of expression
> > drivers/mfd/da8xx_pru.c:61:17: warning: incorrect type in argument 1
> > (different base types)
> > drivers/mfd/da8xx_pru.c:61:17:    expected void const volatile [noderef]
> > <asn:2>*<noident>
> > drivers/mfd/da8xx_pru.c:61:17:    got int
> > drivers/mfd/da8xx_pru.c:66:28: warning: incorrect type in argument 1
> > (different address spaces)
> 
> (Re)read the warning carefully:
> 
> You have to fix drivers/mfd/da8xx_pru.c, the first argument should be
> __void iomem *, not an int. Fix the type of the first argument. Don't
> use any casts at all, follow all warnings, eventually you will have void
> __iomem * (or struct * instead of void *) and no warnings.
> 
> > I can remove all of these by casting to (__force void  __iomem *) but is
> > this correct.
> 
> No evil casts, please :)
In addition, I learned that if a driver is not bound to a specific architecture,
you better use ioread/iowrite & friends, rather that accessing the iomemory
directly.
> 
Kurt

  reply	other threads:[~2011-03-24 13:41 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-08 13:57 [PATCH v3 0/7] pruss mfd drivers Subhasish Ghosh
2011-03-08 13:57 ` [PATCH v3 1/7] mfd: add pruss mfd driver Subhasish Ghosh
2011-03-09 11:56   ` Marc Kleine-Budde
2011-03-24 13:16     ` Subhasish Ghosh
2011-03-24 13:24       ` Marc Kleine-Budde
2011-03-24 13:41         ` Kurt Van Dijck [this message]
2011-03-11 15:28   ` Arnd Bergmann
2011-03-30  7:16     ` Subhasish Ghosh
2011-03-30 10:59       ` Arnd Bergmann
2011-04-05  6:40         ` Subhasish Ghosh
2011-03-30  9:15     ` Subhasish Ghosh
2011-03-30 11:38       ` Arnd Bergmann
2011-03-18 11:59   ` Nori, Sekhar
2011-03-18 12:39     ` Mark Brown
2011-03-22  9:35       ` Nori, Sekhar
2011-03-22  9:43         ` Nori, Sekhar
2011-03-22 16:52         ` Mark Brown
2011-03-08 13:57 ` [PATCH v3 2/7] da850: pruss platform specific additions Subhasish Ghosh
2011-03-08 15:17   ` Sergei Shtylyov
2011-03-08 13:57 ` [PATCH v3 3/7] da850: pruss board " Subhasish Ghosh
2011-03-08 15:19   ` Sergei Shtylyov
2011-03-09  4:29     ` Subhasish Ghosh
2011-03-09 11:59   ` Marc Kleine-Budde
2011-03-08 13:57 ` [PATCH v3 4/7] mfd: pruss SUART private data Subhasish Ghosh
2011-03-08 13:57 ` [PATCH v3 5/7] da850: pruss SUART board specific additions Subhasish Ghosh
2011-03-08 13:57 ` [PATCH v3 6/7] da850: pruss SUART platform " Subhasish Ghosh
2011-03-08 13:57 ` [PATCH v3 7/7] tty: add pruss SUART driver Subhasish Ghosh
2011-03-08 18:47   ` Randy Dunlap
2011-03-15  7:23     ` Subhasish Ghosh
2011-03-18  5:43   ` Subhasish Ghosh
2011-03-18 11:45     ` Alan Cox
2011-03-18 12:07     ` Arnd Bergmann

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=20110324134142.GB27124@e-circ.dyndns.org \
    --to=kurt.van.dijck@eia.be \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).