linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Monakhov <dmonakhov@openvz.org>
To: linux-ext4 <linux-ext4@vger.kernel.org>
Cc: Alex Tomas <alex@clusterfs.com>, devel@openvz.org
Subject: [PATCH 0/3] ext4: Extent code cleanup
Date: Fri, 22 Jun 2007 16:15:09 +0400	[thread overview]
Message-ID: <20070622121509.GA395@localhost.sw.ru> (raw)

Hi, i've finaly found time to review and test ext4 patches.
And i have some fixes:
[1] One more one line fix for ext4-block-reservation patch. IMHO
    it is better to merge it with my previous block reservation fixes.

[2] Fix compilation with EXT_DEBUG

[3] Some code cleanup

             reply	other threads:[~2007-06-22 12:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-22 12:15 Dmitry Monakhov [this message]
2007-06-22 12:17 ` [PATCH 1/3] ext4 block reservation fix3 Dmitry Monakhov
2007-06-25 11:35   ` Alex Tomas
2007-06-22 12:17 ` [PATCH 2/3] extent compilation fixes Dmitry Monakhov
2007-06-25 11:38   ` Alex Tomas
2007-06-22 12:18 ` [PATCH 3/3] ext4: extent macros cleanup Dmitry Monakhov
2007-06-25 11:06   ` Alex Tomas

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=20070622121509.GA395@localhost.sw.ru \
    --to=dmonakhov@openvz.org \
    --cc=alex@clusterfs.com \
    --cc=devel@openvz.org \
    --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).