From: David Howells <dhowells@redhat.com>
To: Andreas Dilger <adilger@sun.com>
Cc: dhowells@redhat.com, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH 23/45] CacheFiles: Be consistent about the use of mapping vs file->f_mapping in Ext3 [ver #41]
Date: Wed, 26 Nov 2008 14:40:37 +0000 [thread overview]
Message-ID: <13588.1227710437@redhat.com> (raw)
In-Reply-To: <20081122173839.GJ3186@webber.adilger.int>
Andreas Dilger <adilger@sun.com> wrote:
> The same patch is needed for ext4.
That doesn't look to be necessary. Ext4 already seems to use mapping rather
than f_mapping in these places.
David
prev parent reply other threads:[~2008-11-26 14:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081120144139.10667.75519.stgit@warthog.procyon.org.uk>
[not found] ` <20081120144338.10667.55564.stgit@warthog.procyon.org.uk>
2008-11-22 17:38 ` [PATCH 23/45] CacheFiles: Be consistent about the use of mapping vs file->f_mapping in Ext3 [ver #41] Andreas Dilger
2008-11-26 14:40 ` David Howells [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=13588.1227710437@redhat.com \
--to=dhowells@redhat.com \
--cc=adilger@sun.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
/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).