Date: Mon, 7 Mar 2016 05:53:56 -0800
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Daeho Jeong <daeho.jeong@samsung.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Question about percpu_free_rwsem function
Message-ID: <20160307135356.GS3577@linux.vnet.ibm.com>
Reply-To: paulmck@linux.vnet.ibm.com
References: <37141218.258171457321291665.JavaMail.weblogic@ep2mlwas02b>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <37141218.258171457321291665.JavaMail.weblogic@ep2mlwas02b>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 776
Lines: 17

On Mon, Mar 07, 2016 at 03:28:11AM +0000, Daeho Jeong wrote:
> Hi,
> 
> I got a trouble while I am developing a patch for EXT4 filesytem.
> Actually, I used a percpu rw semaphore in my patch and there was no
> problem when I built EXT4 filesystem as built-in mode. However, when
> kbuild auto build robot built EXT4 filesystem with my patch as a "module",
> a bulid error occurred because percpu_free_rwsem() function is not exported.
> 
> I noticed that other functions except percpu_free_rwsem() were exported in 2015.
> Is there any reason for percpu_free_rwsem() not to be exported?
> If I need the function to be exported, should I do that in my patch? :-)

Sounds like a question for the ext4 maintainers.  You can find them in
the MAINTAINERS file.

							Thanx, Paul