linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Andy Fleming <afleming@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v2.6.26] powerpc: Fix a bunch of sparse warnings in the qe_lib
Date: Fri, 02 May 2008 13:37:13 -0500	[thread overview]
Message-ID: <481B5F59.8020201@freescale.com> (raw)
In-Reply-To: <1209751415-25612-1-git-send-email-afleming@freescale.com>

Andy Fleming wrote:

>  int ucc_fast_init(struct ucc_fast_info * uf_info, struct ucc_fast_private ** uccf_ret)
>  {
>  	struct ucc_fast_private *uccf;
> -	struct ucc_fast *uf_regs;
> +	struct ucc_fast __iomem *uf_regs;
>  	u32 gumr;
>  	int ret;
>  
> @@ -216,10 +216,10 @@ int ucc_fast_init(struct ucc_fast_info * uf_info, struct ucc_fast_private ** ucc
>  	uccf->stopped_tx = 0;
>  	uccf->stopped_rx = 0;
>  	uf_regs = uccf->uf_regs;
> -	uccf->p_ucce = (u32 *) & (uf_regs->ucce);
> -	uccf->p_uccm = (u32 *) & (uf_regs->uccm);
> +	uccf->p_ucce = (u32 __iomem *) & (uf_regs->ucce);
> +	uccf->p_uccm = (u32 __iomem *) & (uf_regs->uccm);

Since you've already made uf_regs into an __iomem pointer, do you really need to
cast it?

And please remember to CC: me on any QE library patches.

-- 
Timur Tabi
Linux kernel developer at Freescale

  parent reply	other threads:[~2008-05-02 18:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02 18:03 [PATCH v2.6.26] powerpc: Fix a bunch of sparse warnings in the qe_lib Andy Fleming
2008-05-02 18:07 ` Scott Wood
2008-05-02 23:59   ` Andy Fleming
2008-05-02 18:37 ` Timur Tabi [this message]
2008-05-03  0:00   ` Andy Fleming

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=481B5F59.8020201@freescale.com \
    --to=timur@freescale.com \
    --cc=afleming@freescale.com \
    --cc=linuxppc-dev@ozlabs.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).