From: Helge Deller <deller@gmx.de>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Krzysztof Helt <krzysztof.h1@poczta.fm>,
Linux-fbdev-devel <linux-fbdev-devel@lists.sourceforge.net>,
Andrew Morton <akpm@linux-foundation.org>,
linux-parisc@vger.kernel.org
Subject: Re: [RESEND] [PATCH] convert sticore.c to PCI ROM API
Date: Fri, 06 Jun 2008 23:23:10 +0200 [thread overview]
Message-ID: <4849AABE.7040805@gmx.de> (raw)
In-Reply-To: <1212704814.4241.37.camel@localhost.localdomain>
James Bottomley wrote:
>> static struct sti_struct * __devinit
>> -sti_try_rom_generic(unsigned long address, unsigned long hpa, struct pci_dev *pd)
>> +sti_try_rom_generic(unsigned long address, unsigned long hpa,
>> + struct pci_dev *pd)
>> {
>> + char __iomem *rom_base = (char __iomem *) address;
>> struct sti_struct *sti;
>> int ok;
>> - u32 sig;
>> + __le32 sig;
>>
>> if (num_sti_roms >= MAX_STI_ROMS) {
>> printk(KERN_WARNING "maximum number of STI ROMS reached !\n");
>> @@ -808,7 +810,7 @@ test_rom:
>> sig = gsc_readl(address);
>
> Since gsc_readl() has (designedly) no endianness type, doesn't this give
> a sparse warning?
No, it doesn't.
But maybe I tested it wrongly?
[hd@p100 linus-linux-2.6]# REAL_CC=hppa-linux-gcc cgcc -Wbitwise
-Wp,-MD,drivers/video/console/.sticore.o.d -nostdinc -isystem
/opt/palinux33/lib/gcc-lib/hppa-linux/3.3.4/include -D__KERNEL__
-Iinclude -include include/linux/autoconf.h -Wall -Wundef
-Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common
-Werror-implicit-function-declaration -Os -pipe -mno-space-regs
-mfast-indirect-calls -mdisable-fpregs -ffunction-sections -march=1.1
-mschedule=7100LC -fomit-frame-pointer -D"KBUILD_STR(s)=#s"
-D"KBUILD_BASENAME=KBUILD_STR(sticore)"
-D"KBUILD_MODNAME=KBUILD_STR(sticore)" -c -o
drivers/video/console/sticore.o drivers/video/console/sticore.c
drivers/video/console/sticore.c:32:19: warning: symbol 'default_sti' was
not declared. Should it be static?
drivers/video/console/sticore.c:241:1: warning: symbol 'sti_rom_copy'
was not declared. Should it be static?
drivers/video/console/sticore.c:481:24: warning: symbol
'sti_select_fbfont' was not declared. Should it be static?
drivers/video/console/sticore.c:544:24: warning: symbol
'sti_select_font' was not declared. Should it be static?
drivers/video/console/sticore.c:710:16: warning: symbol
'sti_get_wmode_rom' was not declared. Should it be static?
drivers/video/console/sticore.c:727:1: warning: symbol 'sti_read_rom'
was not declared. Should it be static?
drivers/video/console/sticore.c:975:1: warning: symbol 'sti_pci_tbl' was
not declared. Should it be static?
Helge
next prev parent reply other threads:[~2008-06-06 21:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 21:13 [RESEND] [PATCH] convert sticore.c to PCI ROM API Krzysztof Helt
2008-06-05 22:11 ` Andrew Morton
2008-06-06 18:52 ` Krzysztof Helt
2008-06-05 22:26 ` James Bottomley
2008-06-06 20:35 ` Krzysztof Helt
2008-06-06 23:27 ` James Bottomley
2008-06-07 9:08 ` Krzysztof Helt
2008-06-07 20:34 ` Grant Grundler
2008-06-06 21:23 ` Helge Deller [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-06-07 20:51 Jon Smirl
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=4849AABE.7040805@gmx.de \
--to=deller@gmx.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=krzysztof.h1@poczta.fm \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-parisc@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).