From: Guan Xuetao <gxt@mprc.pku.edu.cn>
To: axel.lin@gmail.com
Cc: Michal Marek <mmarek@suse.cz>, Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org,
Alessandro Zummo <a.zummo@towertech.it>,
rtc-linux@googlegroups.com
Subject: Re: [PATCH] rtc: rtc-puv3: Add __devinit and __devexit markers for probe and remove
Date: Tue, 18 Oct 2011 18:35:28 +0800 [thread overview]
Message-ID: <1318934128.1789.46.camel@epip-laptop> (raw)
In-Reply-To: <CAF+7xW=nhutZ7GcSr8j6bT5GZFoKmkmbdRCw+enRKRfPb_bThQ@mail.gmail.com>
On Tue, 2011-10-18 at 16:44 +0800, Axel Lin wrote:
> hi Guan,
>
> > For puv3_rtc_probe, I think it should be in the white-list, but warnings
> > are yielded.
> > For puv3_rtc_remove, the warning could be disappeared by modifying
> > __devexit to __exit, however is it proper?
> >
>
> I'm not able to reproduce it on linux-next tree (20111014).
> If I Enable loadable module support, I got below build error:
>
> CC arch/unicore32/kernel/ksyms.o
> arch/unicore32/kernel/ksyms.c:39: error: 'csum_partial_copy_nocheck'
> undeclared here (not in a function)
> arch/unicore32/kernel/ksyms.c:39: warning: type defaults to 'int' in
> declaration of 'csum_partial_copy_nocheck'
> arch/unicore32/kernel/ksyms.c:40: error: '__csum_ipv6_magic'
> undeclared here (not in a function)
> arch/unicore32/kernel/ksyms.c:40: warning: type defaults to 'int' in
> declaration of '__csum_ipv6_magic'
> arch/unicore32/kernel/ksyms.c:44: error: '__raw_readsb' undeclared
> here (not in a function)
> arch/unicore32/kernel/ksyms.c:44: warning: type defaults to 'int' in
> declaration of '__raw_readsb'
> arch/unicore32/kernel/ksyms.c:47: error: '__raw_readsw' undeclared
> here (not in a function)
> arch/unicore32/kernel/ksyms.c:47: warning: type defaults to 'int' in
> declaration of '__raw_readsw'
> arch/unicore32/kernel/ksyms.c:50: error: '__raw_readsl' undeclared
> here (not in a function)
> arch/unicore32/kernel/ksyms.c:50: warning: type defaults to 'int' in
> declaration of '__raw_readsl'
> arch/unicore32/kernel/ksyms.c:53: error: '__raw_writesb' undeclared
> here (not in a function)
> arch/unicore32/kernel/ksyms.c:53: warning: type defaults to 'int' in
> declaration of '__raw_writesb'
> arch/unicore32/kernel/ksyms.c:56: error: '__raw_writesw' undeclared
> here (not in a function)
> arch/unicore32/kernel/ksyms.c:56: warning: type defaults to 'int' in
> declaration of '__raw_writesw'
> arch/unicore32/kernel/ksyms.c:59: error: '__raw_writesl' undeclared
> here (not in a function)
> arch/unicore32/kernel/ksyms.c:59: warning: type defaults to 'int' in
> declaration of '__raw_writesl'
> arch/unicore32/kernel/ksyms.c:80: error: '__get_user_1' undeclared
> here (not in a function)
> arch/unicore32/kernel/ksyms.c:80: warning: type defaults to 'int' in
> declaration of '__get_user_1'
> arch/unicore32/kernel/ksyms.c:81: error: '__get_user_2' undeclared
> here (not in a function)
> arch/unicore32/kernel/ksyms.c:81: warning: type defaults to 'int' in
> declaration of '__get_user_2'
> arch/unicore32/kernel/ksyms.c:82: error: '__get_user_4' undeclared
> here (not in a function)
> arch/unicore32/kernel/ksyms.c:82: warning: type defaults to 'int' in
> declaration of '__get_user_4'
> arch/unicore32/kernel/ksyms.c:84: error: '__put_user_1' undeclared
> here (not in a function)
> arch/unicore32/kernel/ksyms.c:84: warning: type defaults to 'int' in
> declaration of '__put_user_1'
> arch/unicore32/kernel/ksyms.c:85: error: '__put_user_2' undeclared
> here (not in a function)
> arch/unicore32/kernel/ksyms.c:85: warning: type defaults to 'int' in
> declaration of '__put_user_2'
> arch/unicore32/kernel/ksyms.c:86: error: '__put_user_4' undeclared
> here (not in a function)
> arch/unicore32/kernel/ksyms.c:86: warning: type defaults to 'int' in
> declaration of '__put_user_4'
> arch/unicore32/kernel/ksyms.c:87: error: '__put_user_8' undeclared
> here (not in a function)
> arch/unicore32/kernel/ksyms.c:87: warning: type defaults to 'int' in
> declaration of '__put_user_8'
> make[1]: *** [arch/unicore32/kernel/ksyms.o] Error 1
> make: *** [arch/unicore32/kernel] Error 2
This output seems that there is no cross-compiler in your machine.
And the cross-compiler could be downloaded from my website:
http://mprc.pku.edu.cn/~guanxuetao/linux/uc4-1.0.5-hard.tgz
(about 100MB, including glibc for unicore32)
>
> I also try to clone unicore tree, but I got connection timed out. :-(
>
> axel@phoenix:~/repos/git$ git clone
> git://master.kernel.org/pub/scm/linux/kernel/git/epip/linux-unicore.git
> Cloning into linux-unicore...
> master.kernel.org[0: 140.211.167.34]: errno=Connection timed out
> fatal: unable to connect a socket (Connection timed out)
Sorry, I just notify the email by Peter Anvin.
And I will re-establish my PGP and repo recently.
Thanks,
Guan Xuetao
>
> Regards,
> Axel
next prev parent reply other threads:[~2011-10-18 10:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 14:29 [PATCH] rtc: rtc-puv3: Add __devinit and __devexit markers for probe and remove Axel Lin
2011-10-11 10:25 ` Guan Xuetao
2011-10-12 2:58 ` Guan Xuetao
2011-10-18 7:22 ` Guan Xuetao
2011-10-18 8:44 ` Axel Lin
2011-10-18 10:35 ` Guan Xuetao [this message]
2011-10-21 8:32 ` Michal Marek
2011-10-21 8:42 ` Michal Marek
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=1318934128.1789.46.camel@epip-laptop \
--to=gxt@mprc.pku.edu.cn \
--cc=a.zummo@towertech.it \
--cc=arnd@arndb.de \
--cc=axel.lin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=rtc-linux@googlegroups.com \
/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