From: Nick Piggin <npiggin@suse.de>
To: Minchan Kim <minchan.kim@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Anton Altaparmakov <aia21@cantab.net>,
Al Viro <viro@zeniv.linux.org.uk>, Jiri Kosina <jkosina@suse.cz>,
Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org,
linux-ntfs-dev@lists.sourceforge.net
Subject: Re: [PATCH 2/2] ntfs: use add_to_page_cache_lru
Date: Wed, 7 Apr 2010 03:11:21 +1000 [thread overview]
Message-ID: <20100406171121.GI5288@laptop> (raw)
In-Reply-To: <r2s28c262361004060930u95af7d62k5136aeb67c8d7019@mail.gmail.com>
On Wed, Apr 07, 2010 at 01:30:24AM +0900, Minchan Kim wrote:
> Hi, Nick.
>
> On Wed, Apr 7, 2010 at 12:47 AM, Nick Piggin <npiggin@suse.de> wrote:
> > On Tue, Apr 06, 2010 at 12:46:05AM +0900, Minchan Kim wrote:
> >>
> >> While I discuss exportable add_to_page_cache_lru,
> >> http://marc.info/?l=linux-mm&m=127047788612445&w=2
> >> I found that
> >> http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg04472.html.
> >>
> >> Let's change to use it in ntfs.
> >
> > Thanks, I went through most filesystems and changed it in those too,
> > including ntfs. Haven't had much feedback but I'll just send the
> > patches to Andrew if they haven't been merged by next release.
> >
>
> Please, let me know it.
> That's because actually I had a plan to change about some filesystem.
> If you already did it, I don't need to do. :)
I did most of them and cc'ed linux-fsdevel last month. btrfs, cifs,
nfs, ntfs. If you find any others, fix em up :)
prev parent reply other threads:[~2010-04-06 17:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 15:46 [PATCH 2/2] ntfs: use add_to_page_cache_lru Minchan Kim
2010-04-06 15:47 ` Nick Piggin
2010-04-06 16:30 ` Minchan Kim
2010-04-06 17:11 ` Nick Piggin [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=20100406171121.GI5288@laptop \
--to=npiggin@suse.de \
--cc=aia21@cantab.net \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=minchan.kim@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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.