From: Sascha Hauer <s.hauer@pengutronix.de>
To: Belisko Marek <marek.belisko@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: sparse warnings
Date: Wed, 17 Nov 2010 10:11:02 +0100 [thread overview]
Message-ID: <20101117091102.GS6017@pengutronix.de> (raw)
In-Reply-To: <AANLkTinH6kLH99A0DgUCp3AFnrLsmcACMeTgW1s1PNKt@mail.gmail.com>
Hi Marek,
On Mon, Nov 15, 2010 at 03:20:47PM +0100, Belisko Marek wrote:
> Hi,
>
> barebox compilation with C=1 produce a lot of sparse warnings.
> Mainly concerning __iomem problems with readb() and similar functions.
>
> Make it sense to take care or just could be omitted?
I think it makes sense to work on this. Then we can see the useful
warnings buried under the __iomem warnings.
I had the idea of adding a
#define IOMEM(addr) ((void __force __iomem *)(addr))
and use it where appropriate.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2010-11-17 9:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 14:20 sparse warnings Belisko Marek
2010-11-17 9:11 ` Sascha Hauer [this message]
2010-11-18 9:36 ` Belisko Marek
2010-11-18 10:01 ` Sascha Hauer
2010-11-18 10:22 ` Uwe Kleine-König
-- strict thread matches above, loose matches on Subject: below --
2020-08-04 21:36 Michael S. Tsirkin
2020-07-29 19:48 Bjorn Helgaas
2020-09-30 22:39 ` Bjorn Helgaas
2020-10-01 6:29 ` Kishon Vijay Abraham I
2008-10-28 15:57 Johannes Berg
2008-10-29 8:06 ` Holger Schurig
2008-09-11 10:46 Johannes Berg
2008-06-27 19:52 Sparse warnings Larry Finger
2008-06-27 19:53 ` Pavel Roskin
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=20101117091102.GS6017@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=marek.belisko@gmail.com \
/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.