From: Valdis.Kletnieks@vt.edu
To: "N.P.S. N.P.S." <napohybelskurwysynom2010@gmail.com>
Cc: akpm@linux-foundation.org, mm-commits@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: mmotm 2010-09-28-16-13 uploaded
Date: Tue, 28 Sep 2010 20:49:44 -0400 [thread overview]
Message-ID: <124506.1285721384@localhost> (raw)
In-Reply-To: Your message of "Wed, 29 Sep 2010 02:27:55 +0200." <AANLkTimFbxc7MGdirSzdJ-YZbFFHBVn4JJhHcP46W1_4@mail.gmail.com>
On Wed, 29 Sep 2010 02:27:55 +0200, "N.P.S. N.P.S." said:
> Hi,
>
> 2010/9/29 <akpm@linux-foundation.org>:
> > The mm-of-the-moment snapshot 2010-09-28-16-13 has been uploaded to
>
> I wonder why are these two functions in include/linux/fs.h
> static inline void lock_flocks()
> {
> }
>
> static inline void unlock_flocks()
> {
> }
Those were added as part of the kill-the-BKL project. They used to be
done as #defines to lock_kernel and unlock_kernel, but became full-fledged
functions in this release. Unfortunately, if you build with CONFIG_FILE_LOCKING=n
you need to provide a dummy stub, which is what was intended here.
Does the following (untested) fix the problem for you?
Signed-Off-By: Valdis Kletnieks <valdis.kletnieks@vt.edu>
--- linux-2.6.36-rc5-mmotm0928/include/linux/fs.h.dist 2010-09-28 20:46:29.276970365 -0400
+++ linux-2.6.36-rc5-mmotm0928/include/linux/fs.h 2010-09-28 20:47:34.221924470 -0400
@@ -1274,11 +1274,11 @@ static inline int lock_may_write(struct
return 1;
}
-static inline void lock_flocks()
+static inline void lock_flocks(void)
{
}
-static inline void unlock_flocks()
+static inline void unlock_flocks(void)
{
}
next prev parent reply other threads:[~2010-09-29 0:50 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 23:13 mmotm 2010-09-28-16-13 uploaded akpm
2010-09-29 0:27 ` N.P.S. N.P.S.
2010-09-29 0:44 ` Andrew Morton
2010-09-29 12:19 ` Arnd Bergmann
2010-09-29 12:57 ` N.P.S. N.P.S.
2010-09-29 0:49 ` Valdis.Kletnieks [this message]
2010-09-29 0:57 ` N.P.S. N.P.S.
2010-09-29 1:19 ` Valdis.Kletnieks
2010-09-29 0:49 ` N.P.S. N.P.S.
2010-09-29 1:13 ` Randy Dunlap
2010-09-29 5:55 ` Andrew Morton
2010-09-29 1:25 ` Valdis.Kletnieks
2010-09-29 9:15 ` N.P.S. N.P.S.
2010-09-29 15:00 ` Randy Dunlap
2010-09-29 15:04 ` Na Pohybel
[not found] ` <AANLkTikk+k7WJEDv9dQoJDyMdz8NCM8LOb5kW=xyWK71@mail.gmail.com>
2010-09-29 9:17 ` Fwd: " N.P.S. N.P.S.
2010-09-29 13:13 ` N.P.S. N.P.S.
2010-09-29 15:01 ` Randy Dunlap
2010-09-29 15:05 ` Na Pohybel
2010-09-30 16:59 ` Na Pohybel
2010-09-30 18:25 ` N.P.S.
2010-09-30 19:39 ` N.P.S.
2010-10-01 15:40 ` Zimny Lech
2010-10-04 13:43 ` Zimny Lech
2010-10-04 23:16 ` Andrew Morton
2010-10-04 23:33 ` Zimny Lech
2010-10-04 23:43 ` Andrew Morton
2010-10-20 21:58 ` [PATCH] Removal of duplicate includes from many files N.P.S.
2010-10-20 23:15 ` Andrew Morton
2010-10-20 23:25 ` Zimny Lech
2010-10-24 1:48 ` mmotm 2010-09-28-16-13 uploaded Maciej W. Rozycki
2010-10-05 0:46 ` Stephen Rothwell
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=124506.1285721384@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=napohybelskurwysynom2010@gmail.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;
as well as URLs for NNTP newsgroup(s).