From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 01/12] ARM: animeo_ip: Use __iomem specifier for memory pointer
Date: Wed, 29 Jan 2014 18:51:30 +0100 [thread overview]
Message-ID: <20140129175130.GB9671@ns203013.ovh.net> (raw)
In-Reply-To: <20140129092353.GH16215@pengutronix.de>
On 10:23 Wed 29 Jan , Sascha Hauer wrote:
> Hi Alexander,
>
> from this series I applied:
>
> ARM: uncompress: Remove unused variable
>
> cleanup
>
> ARM: animeo_ip: Use __iomem specifier for memory pointer
> ARM: at91: irq_fixup: Use __iomem specifier for memory pointer
> ARM: i.MX: external_nand_boot: Use __iomem specifier for memory pointer
> ARM: i.MX: esdctl: Use __iomem specifier for memory pointer
> ARM: i.MX: esdctl-v4: Use __iomem specifier for memory pointer
>
> These are cases in which registers are accessed and __iomem should be
> used.
>
> For the remaining I am unsure as it's RAM that's accessed there. I don't
> think these should have __iomem.
__iomem is for register access not ram access
Best Regards,
J.
>
> 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
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2014-01-29 17:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-25 19:34 Alexander Shiyan
2014-01-25 19:34 ` [PATCH 02/12] ARM: guf-cupid: " Alexander Shiyan
2014-01-25 19:34 ` [PATCH 03/12] ARM: tqma6x: " Alexander Shiyan
2014-01-25 19:34 ` [PATCH 04/12] ARM: uncompress: Remove unused variable Alexander Shiyan
2014-01-25 19:34 ` [PATCH 05/12] ARM: PBL: Use __iomem specifier for memory pointer Alexander Shiyan
2014-01-25 19:34 ` [PATCH 06/12] lib: bootz: " Alexander Shiyan
2014-01-25 19:34 ` [PATCH 07/12] lib: bootm: " Alexander Shiyan
2014-01-25 19:34 ` [PATCH 08/12] ARM: at91: boot_test_cmd: " Alexander Shiyan
2014-01-29 17:50 ` Jean-Christophe PLAGNIOL-VILLARD
2014-01-25 19:34 ` [PATCH 09/12] ARM: at91: irq_fixup: " Alexander Shiyan
2014-01-25 19:34 ` [PATCH 10/12] ARM: i.MX: external_nand_boot: " Alexander Shiyan
2014-01-25 19:34 ` [PATCH 11/12] ARM: i.MX: esdctl: " Alexander Shiyan
2014-01-25 19:34 ` [PATCH 12/12] ARM: i.MX: esdctl-v4: " Alexander Shiyan
2014-01-29 9:23 ` [PATCH 01/12] ARM: animeo_ip: " Sascha Hauer
2014-01-29 17:51 ` Jean-Christophe PLAGNIOL-VILLARD [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=20140129175130.GB9671@ns203013.ovh.net \
--to=plagnioj@jcrosoft.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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