From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] powerpc/p1_p2_rdb_pc: Fix warnings for __iomem pointers
Date: Wed, 11 Dec 2013 11:17:48 -0800 [thread overview]
Message-ID: <52A8BA5C.1000202@freescale.com> (raw)
In-Reply-To: <1386667342-24464-1-git-send-email-claudiu.manoil@freescale.com>
On 12/10/2013 01:22 AM, Claudiu Manoil wrote:
> Add the __iomem address space marker for the tsec pointers
> to struct tsec_mii_mng memory mapped register regions.
> This solves the sparse warnings for mixig normal pointers with
> __iomem pointers for tsec.
>
> p1_p2_rdb_pc.c:373:24: warning: incorrect type in assignment (different
> address spaces)
> p1_p2_rdb_pc.c:373:24: expected struct tsec_mii_mng [noderef]
> <asn:2>*regs
> p1_p2_rdb_pc.c:373:24: got struct tsec_mii_mng *<noident>
>
> Use TSEC_GET_MDIO_REGS_BASE() for the remaining mdio 'regs'
> initializations to remove the __iomem warnings and for consistency.
>
> Signed-off-by: Claudiu Manoil <claudiu.manoil@freescale.com>
> ---
Applied to u-boot-mpc85xx/master. Thanks.
York
prev parent reply other threads:[~2013-12-11 19:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 9:22 [U-Boot] [PATCH] powerpc/p1_p2_rdb_pc: Fix warnings for __iomem pointers Claudiu Manoil
2013-12-11 19:17 ` York Sun [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=52A8BA5C.1000202@freescale.com \
--to=yorksun@freescale.com \
--cc=u-boot@lists.denx.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