From: Rince <rincebrain@gmail.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Nick Piggin <npiggin@suse.de>,
Ravikiran G Thirumalai <kiran@scalex86.org>,
Sage Weil <sage@newdream.net>,
linux-fsdevel@vger.kernel.org,
Linux Memory Management List <linux-mm@kvack.org>,
stable@kernel.org
Subject: Re: [patch] mm: close page_mkwrite races (try 3)
Date: Thu, 30 Apr 2009 10:33:54 -0400 [thread overview]
Message-ID: <5da0588e0904300733t313b9168s634dfd51fc8a5b60@mail.gmail.com> (raw)
In-Reply-To: <5da0588e0904300722p538cb174xcc01bbe85dd58ec8@mail.gmail.com>
On Thu, Apr 30, 2009 at 10:22 AM, Rince <rincebrain@gmail.com> wrote:
> four patches mentioned
Hm, somehow I missed that the NFS 3-liner above wasn't included in the
four patches.
Let's see how this goes. Apologies for the misunderstanding. :)
- Rich
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-04-30 14:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 7:11 [patch] mm: close page_mkwrite races (try 2) Nick Piggin
2009-04-14 7:11 ` Nick Piggin
2009-04-15 8:25 ` [patch] mm: close page_mkwrite races (try 3) Nick Piggin
2009-04-15 8:25 ` Nick Piggin
2009-04-16 1:38 ` Andrew Morton
2009-04-16 2:03 ` Nick Piggin
2009-04-16 2:03 ` Nick Piggin
2009-04-16 2:23 ` Nick Piggin
2009-04-28 18:57 ` Ravikiran G Thirumalai
2009-04-29 7:12 ` Nick Piggin
2009-04-29 7:12 ` Nick Piggin
2009-04-29 7:24 ` Andrew Morton
2009-04-29 7:45 ` Nick Piggin
2009-04-29 12:39 ` Trond Myklebust
2009-04-29 15:27 ` Andrew Morton
2009-04-29 16:45 ` Trond Myklebust
2009-04-29 16:45 ` Trond Myklebust
2009-04-30 14:22 ` Rince
2009-04-30 14:22 ` Rince
2009-04-30 14:33 ` Rince [this message]
2009-05-02 22:12 ` Rince
2009-05-03 1:38 ` Trond Myklebust
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=5da0588e0904300733t313b9168s634dfd51fc8a5b60@mail.gmail.com \
--to=rincebrain@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=kiran@scalex86.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--cc=sage@newdream.net \
--cc=stable@kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.