linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Bordug <vbordug@ru.mvista.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>,
	Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 3/5] [FS_ENET] OF-related update for FEC and SCC MAC's
Date: Wed, 10 Jan 2007 23:14:21 +0300	[thread overview]
Message-ID: <20070110231421.6c6ec86c@localhost.localdomain> (raw)
In-Reply-To: <CE5804BC-675C-474A-B74B-62E6B8E0D9F2@kernel.crashing.org>

[-- Attachment #1: Type: text/plain, Size: 1359 bytes --]

On Wed, 10 Jan 2007 11:07:58 -0600
Kumar Gala wrote:

> 
> On Jan 9, 2007, at 7:11 PM, Vitaly Bordug wrote:
> 
> >
> > Updated direct resource pass with ioremap call, make it grant  
> > proper IRQ
> > mapping, stuff incompatible with the new approach were
> > respectively put  under
> > #ifndef CONFIG_PPC_MERGE.
> >
> > Signed-off-by: Vitaly Bordug <vbordug@ru.mvista.com>
> > ---
> >
> >  drivers/net/fs_enet/mac-fec.c |   13 +++++++++----
> >  drivers/net/fs_enet/mac-scc.c |    6 ++++--
> >  drivers/net/phy/fixed.c       |    2 +-
> >  3 files changed, 14 insertions(+), 7 deletions(-)
> >
> > diff --git a/drivers/net/fs_enet/mac-fec.c b/drivers/net/fs_enet/ 
> > mac-fec.c
> > index c2c5fd4..474d6d7 100644
> > --- a/drivers/net/fs_enet/mac-fec.c
> > +++ b/drivers/net/fs_enet/mac-fec.c
> > @@ -104,9 +104,9 @@ static int do_pd_setup(struct fs_enet_private  
> > *fep)
> >  	fep->interrupt = platform_get_irq_byname(pdev,"interrupt");
> >  	if (fep->interrupt < 0)
> >  		return -EINVAL;
> > -	
> > +
> >  	r = platform_get_resource_byname(pdev, IORESOURCE_MEM,
> > "regs");
> > -	fep->fec.fecp =(void*)r->start;
> > +	fep->fec.fecp = (void *)ioremap(r->start, r->end -
> > r->start + 1);
> 
> you should get rid of the (void *) cast
> 

Here and below: 
Agreed; will fix and respin.


Thanks, 
Vitaly

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-01-10 20:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-10  1:11 [PATCH 1/5] [POWERPC] cpm2: Updates for CPM2 pic Vitaly Bordug
2007-01-10  1:11 ` [PATCH 2/5] [POWERPC] cpm_uart: OF-related updates Vitaly Bordug
2007-01-10  1:11 ` [PATCH 3/5] [FS_ENET] OF-related update for FEC and SCC MAC's Vitaly Bordug
2007-01-10 17:07   ` Kumar Gala
2007-01-10 20:14     ` Vitaly Bordug [this message]
2007-01-10  1:12 ` [PATCH 4/5] [POWERPC] Fix kernel build errors for mpc8272ads and mpc8560ads Vitaly Bordug
2007-01-10 17:11   ` Kumar Gala
2007-01-10 20:50     ` Vitaly Bordug
2007-01-10 20:58       ` Kumar Gala
2007-01-10 21:41         ` Vitaly Bordug
2007-01-10  1:12 ` [PATCH 5/5] [POWERPC] mpc8272ads: defconfig Vitaly Bordug
2007-01-10  2:13 ` [PATCH 1/5] [POWERPC] cpm2: Updates for CPM2 pic Paul Mackerras
2007-01-10  5:09   ` Vitaly Bordug
2007-01-10 17:02 ` Kumar Gala
2007-01-10 20:13   ` Vitaly Bordug
2007-01-10 20:55     ` Kumar Gala
2007-01-10 20:58       ` Vitaly Bordug

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=20070110231421.6c6ec86c@localhost.localdomain \
    --to=vbordug@ru.mvista.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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).