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
Date: Mon, 7 Mar 2016 05:53:56 -0800 [thread overview]
Message-ID: <20160307135356.GS3577@linux.vnet.ibm.com> (raw)
In-Reply-To: <37141218.258171457321291665.JavaMail.weblogic@ep2mlwas02b>
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
prev parent reply other threads:[~2016-03-07 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 3:28 Question about percpu_free_rwsem function Daeho Jeong
2016-03-07 13:53 ` Paul E. McKenney [this message]
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=20160307135356.GS3577@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=daeho.jeong@samsung.com \
--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