From: Javier Herrero <jherrero@hvsistemas.es>
To: unlisted-recipients:; (no To-header on input)
Cc: Bryan Wu <cooloney@kernel.org>,
jeff@garzik.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] netdev: DM9000: Added typecasting to supress some warnings on Blackfin
Date: Mon, 13 Oct 2008 11:28:23 +0200 [thread overview]
Message-ID: <48F314B7.3020708@hvsistemas.es> (raw)
In-Reply-To: <20081013091725.GG31627@trinity.fluff.org>
Hi, Bryan,
So it seems that we must correct that in other place?
Regards,
Javier
Ben Dooks escribió:
> On Mon, Oct 13, 2008 at 05:10:09PM +0800, Bryan Wu wrote:
>> From: Javier Herrero <jherrero@hvsistemas.es>
>
> No, your arch definitions of writesb and co are wrong if they
> are not taking 'void __iomem *' arguments.
>
>> Signed-off-by: Javier Herrero <jherrero@hvsistemas.es>
>> Signed-off-by: Bryan Wu <cooloney@kernel.org>
>> ---
>> drivers/net/dm9000.c | 12 ++++++------
>> 1 files changed, 6 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/net/dm9000.c b/drivers/net/dm9000.c
>> index f42c23f..c4737ca 100644
>> --- a/drivers/net/dm9000.c
>> +++ b/drivers/net/dm9000.c
>> @@ -188,35 +188,35 @@ iow(board_info_t * db, int reg, int value)
>>
>> static void dm9000_outblk_8bit(void __iomem *reg, void *data, int count)
>> {
>> - writesb(reg, data, count);
>> + writesb((int)reg, data, count);
>> }
>>
>> static void dm9000_outblk_16bit(void __iomem *reg, void *data, int count)
>> {
>> - writesw(reg, data, (count+1) >> 1);
>> + writesw((int)reg, data, (count+1) >> 1);
>> }
>>
>> static void dm9000_outblk_32bit(void __iomem *reg, void *data, int count)
>> {
>> - writesl(reg, data, (count+3) >> 2);
>> + writesl((int)reg, data, (count+3) >> 2);
>> }
>>
>> /* input block from chip to memory */
>>
>> static void dm9000_inblk_8bit(void __iomem *reg, void *data, int count)
>> {
>> - readsb(reg, data, count);
>> + readsb((int)reg, data, count);
>> }
>>
>>
>> static void dm9000_inblk_16bit(void __iomem *reg, void *data, int count)
>> {
>> - readsw(reg, data, (count+1) >> 1);
>> + readsw((int)reg, data, (count+1) >> 1);
>> }
>>
>> static void dm9000_inblk_32bit(void __iomem *reg, void *data, int count)
>> {
>> - readsl(reg, data, (count+3) >> 2);
>> + readsl((int)reg, data, (count+3) >> 2);
>> }
>>
>> /* dump block from chip to null */
>> --
>> 1.5.6
>
--
------------------------------------------------------------------------
Javier Herrero EMAIL: jherrero@hvsistemas.com
HV Sistemas S.L. PHONE: +34 949 336 806
Los Charcones, 17A FAX: +34 949 336 792
19170 El Casar - Guadalajara - Spain WEB: http://www.hvsistemas.com
next prev parent reply other threads:[~2008-10-13 9:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 9:10 [PATCH 1/1] netdev: DM9000: Added typecasting to supress some warnings on Blackfin Bryan Wu
2008-10-13 9:17 ` Ben Dooks
2008-10-13 9:28 ` Javier Herrero [this message]
2008-10-13 9:52 ` Bryan Wu
2008-10-13 10:24 ` Mike Frysinger
2008-10-13 10:27 ` Bryan Wu
2008-10-13 9:51 ` Bryan Wu
2008-10-13 10:01 ` David Miller
2008-10-13 23:18 ` Ben Dooks
2008-10-13 12:41 ` Stephen Hemminger
2008-10-14 8:50 ` Bryan Wu
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=48F314B7.3020708@hvsistemas.es \
--to=jherrero@hvsistemas.es \
--cc=cooloney@kernel.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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).