public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 21:19:20 -0400	[thread overview]
Message-ID: <137549.1285723160@localhost> (raw)
In-Reply-To: Your message of "Wed, 29 Sep 2010 02:57:59 +0200." <AANLkTin+JRpTZsFO-neZ1Di=tskGK2Ne=xEKKpZrRB1C@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]

On Wed, 29 Sep 2010 02:57:59 +0200, "N.P.S. N.P.S." said:
> 2010/9/29  <Valdis.Kletnieks@vt.edu>:
> > On Wed, 29 Sep 2010 02:27:55 +0200, "N.P.S. N.P.S." said:
> >> Hi,
> >>
> >> 2010/9/29 =A0<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. =A0They used to be
> > done as #defines to lock_kernel and unlock_kernel, but became full-fledge=
> d
> > functions in this release. =A0Unfortunately, if you build with CONFIG_FIL=
> E_LOCKING=3Dn
> > you need to provide a dummy stub, which is what was intended here.
> >
> > Does the following (untested) fix the problem for you?
> 
> Yes, it does. Thanks!

And right after that I spotted that Randy Dunlap posted an almost identical
patch (with better changelog) earlier this afternoon...

[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2010-09-29  1:20 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
2010-09-29  0:57     ` N.P.S. N.P.S.
2010-09-29  1:19       ` Valdis.Kletnieks [this message]
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=137549.1285723160@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