From: Joel Becker <jlbec@evilplan.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Marco Stornelli <marco.stornelli@gmail.com>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Mark Fasheh <mfasheh@suse.com>,
ocfs2-devel@oss.oracle.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 06/21] ocfs2: drop vmtruncate
Date: Wed, 24 Oct 2012 17:17:32 -0700 [thread overview]
Message-ID: <20121025001731.GB3140@localhost> (raw)
In-Reply-To: <20121023130237.GA21594@infradead.org>
On Tue, Oct 23, 2012 at 09:02:38AM -0400, Christoph Hellwig wrote:
> On Tue, Oct 23, 2012 at 01:54:48AM -0700, Joel Becker wrote:
> > On Sat, Oct 20, 2012 at 02:19:00PM +0200, Marco Stornelli wrote:
> > > Removed vmtruncate
> > >
> > > Signed-off-by: Marco Stornelli <marco.stornelli@gmail.com>
> >
> > Acked-by: Joel Becker <jlbec@evilplan.org>
> >
> > Do you want me to pull this, or are you going to send it with your set?
>
> Is this really correct? It now updates i_size before starting a
> transaction.
Ok, I missed that, and I need to re-check.
Joel
--
"If at first you don't succeed, cover all traces that you tried."
-Unknown
http://www.jlbec.org/
jlbec@evilplan.org
next prev parent reply other threads:[~2012-10-25 0:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-20 12:19 [PATCH 06/21] ocfs2: drop vmtruncate Marco Stornelli
2012-10-23 8:54 ` Joel Becker
2012-10-23 8:58 ` Marco Stornelli
2012-10-23 9:02 ` Joel Becker
2012-10-23 12:48 ` Marco Stornelli
2012-10-25 0:18 ` Joel Becker
2012-10-25 6:37 ` Marco Stornelli
2012-10-23 13:02 ` Christoph Hellwig
2012-10-25 0:17 ` Joel Becker [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-12-15 10:50 Marco Stornelli
2012-11-03 9:25 Marco Stornelli
2012-08-31 13:54 Marco Stornelli
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=20121025001731.GB3140@localhost \
--to=jlbec@evilplan.org \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.stornelli@gmail.com \
--cc=mfasheh@suse.com \
--cc=ocfs2-devel@oss.oracle.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;
as well as URLs for NNTP newsgroup(s).