From: Andrew Morton <akpm@linux-foundation.org>
To: "N.P.S. N.P.S." <napohybelskurwysynom2010@gmail.com>
Cc: linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: mmotm 2010-09-28-16-13 uploaded
Date: Tue, 28 Sep 2010 17:44:59 -0700 [thread overview]
Message-ID: <20100928174459.53c5a865.akpm@linux-foundation.org> (raw)
In-Reply-To: <AANLkTimFbxc7MGdirSzdJ-YZbFFHBVn4JJhHcP46W1_4@mail.gmail.com>
On Wed, 29 Sep 2010 02:27:55 +0200 "N.P.S. N.P.S." <napohybelskurwysynom2010@gmail.com> wrote:
> 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()
> {
> }
>
> Was there any contest for function, which will cause many warnings?
>
> I'm getting an awful lot of
> CC kernel/trace/trace_sched_switch.o
> In file included from kernel/trace/trace_sched_switch.c:8:
> include/linux/fs.h:1278: warning: function declaration isn___t a prototype
> include/linux/fs.h:1282: warning: function declaration isn___t a prototype
> CC kernel/trace/trace_functions.o
> In file included from include/linux/debugfs.h:18,
> from kernel/trace/trace_functions.c:13:
> include/linux/fs.h:1278: warning: function declaration isn___t a prototype
> include/linux/fs.h:1282: warning: function declaration isn___t a prototype
Arnd has been bad.
commit 0a4de5980db88de75b798b291524ba9af8553e7c
Author: Arnd Bergmann <arnd@arndb.de>
AuthorDate: Sat Sep 18 15:09:31 2010 +0200
Commit: Arnd Bergmann <arnd@arndb.de>
CommitDate: Sat Sep 25 18:07:47 2010 +0200
fs/locks.c: prepare for BKL removal
next prev parent reply other threads:[~2010-09-29 0:44 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 23:13 akpm
2010-09-29 0:27 ` N.P.S. N.P.S.
2010-09-29 0:44 ` Andrew Morton [this message]
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
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=20100928174459.53c5a865.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@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
Powered by JetHome