From: Guan Xuetao <gxt@mprc.pku.edu.cn>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org, greg@kroah.com
Subject: Re: [PATCH] unicore32: fix build error for find bitops
Date: Mon, 13 Jun 2011 18:22:38 +0800 [thread overview]
Message-ID: <1307960558.1878.21.camel@epip-laptop> (raw)
In-Reply-To: <BANLkTim7znORJyhM2D9r7+p0CiYc+RL97Q@mail.gmail.com>
On Mon, 2011-06-13 at 18:33 +0900, Akinobu Mita wrote:
> 2011/6/13 Guan Xuetao <gxt@mprc.pku.edu.cn>:
> > Thanks, please review following patch:
>
> Looks good to me.
Could I add your acked-by information on this patch?
>
> > diff --git a/arch/unicore32/kernel/ksyms.c
> > b/arch/unicore32/kernel/ksyms.c
> > index a897080..d98bd81 100644
> > --- a/arch/unicore32/kernel/ksyms.c
> > +++ b/arch/unicore32/kernel/ksyms.c
> > @@ -24,8 +24,8 @@
> >
> > #include "ksyms.h"
> >
> > -EXPORT_SYMBOL(__uc32_find_next_zero_bit);
> > -EXPORT_SYMBOL(__uc32_find_next_bit);
> > +EXPORT_SYMBOL(find_next_zero_bit);
> > +EXPORT_SYMBOL(find_next_bit);
>
> I'm wondering why there are no EXPORT_SYMBOL for find_first_bit
> and find_first_zero_bit.
IMO, only functions that are needed by modules should be exported.
When building modules under unicore32 & pkunity-soc, we only need
find_next_bit and find_next_zero_bit exported at present, and if new
functions are required, I am going to add them in the same time.
In fact, I think, the 'arch-generic' ksyms.c is a better idea.
Guan Xuetao
next prev parent reply other threads:[~2011-06-13 10:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 11:09 [PATCH] unicore32: fix build error for find bitops GuanXuetao
2011-06-09 11:09 ` GuanXuetao
2011-06-09 11:32 ` Akinobu Mita
2011-06-09 14:05 ` Akinobu Mita
2011-06-10 3:16 ` Guan Xuetao
2011-06-10 4:22 ` Akinobu Mita
2011-06-13 8:57 ` Guan Xuetao
2011-06-13 8:57 ` Guan Xuetao
2011-06-13 9:33 ` Akinobu Mita
2011-06-13 10:22 ` Guan Xuetao [this message]
2011-06-13 11:32 ` Akinobu Mita
2011-06-10 3:13 ` Guan Xuetao
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=1307960558.1878.21.camel@epip-laptop \
--to=gxt@mprc.pku.edu.cn \
--cc=akinobu.mita@gmail.com \
--cc=arnd@arndb.de \
--cc=greg@kroah.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@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