linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ted Ts'o <tytso@mit.edu>
To: Lukas Czerner <lczerner@redhat.com>
Cc: linux-ext4@vger.kernel.org, k-mio@sx.jp.nec.com,
	achender@linux.vnet.ibm.com
Subject: Re: [PATCH 1/2] ext4: Fix max file size and logical block counting of extent format file
Date: Mon, 6 Jun 2011 00:09:36 -0400	[thread overview]
Message-ID: <20110606040936.GF7180@thunk.org> (raw)
In-Reply-To: <1307128825-3013-1-git-send-email-lczerner@redhat.com>

Thanks, added to the ext4 tree.

					- Ted

      parent reply	other threads:[~2011-06-06  4:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-03 19:20 [PATCH 1/2] ext4: Fix max file size and logical block counting of extent format file Lukas Czerner
2011-06-03 19:20 ` [PATCH 2/2] ext4: in fiemap use FIEMAP_EXTENT_LAST flag for last extent Lukas Czerner
2011-06-04  0:13   ` Allison Henderson
2011-06-06  4:09   ` Ted Ts'o
2011-06-06  4:09 ` Ted Ts'o [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=20110606040936.GF7180@thunk.org \
    --to=tytso@mit.edu \
    --cc=achender@linux.vnet.ibm.com \
    --cc=k-mio@sx.jp.nec.com \
    --cc=lczerner@redhat.com \
    --cc=linux-ext4@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).