DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=pyBnY8Uej2FhWjVu+dJe5Fak6dwsHLoEjjFPqaNKwxvDkQJQEKzBF5YLURyd+MrR8w
         oaSINspdDCwQTjlwMOzcHmAGGT6bfNZZ/FY0vLBrnKmcNgQdXKVCvj+a0Jykwo7yQel0
         IIGJi3SKGjZgLPJW2Xmdy8ypW74Nx0bksHloI=
MIME-Version: 1.0
In-Reply-To: <1307955422.1878.3.camel@epip-laptop>
References: <1307617752-23426-1-git-send-email-gxt@mprc.pku.edu.cn>
	<BANLkTikNC8uh-X_0iJZH3tYd_kf46W1Rwg@mail.gmail.com>
	<BANLkTimWYjzxhQBH2A76D590KBfjKbguTA@mail.gmail.com>
	<1307675815.1537.9.camel@epip-laptop>
	<BANLkTi=aVFisCuS-W-4iNSmDVCtKOWD5_w@mail.gmail.com>
	<1307955422.1878.3.camel@epip-laptop>
Date: Mon, 13 Jun 2011 18:33:51 +0900
Message-ID: <BANLkTim7znORJyhM2D9r7+p0CiYc+RL97Q@mail.gmail.com>
Subject: Re: [PATCH] unicore32: fix build error for find bitops
From: Akinobu Mita <akinobu.mita@gmail.com>
To: gxt@mprc.pku.edu.cn
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
        greg@kroah.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 830
Lines: 26

2011/6/13 Guan Xuetao <gxt@mprc.pku.edu.cn>:
> Thanks, please review following patch:

Looks good to me.

> 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/