From: tytso@mit.edu
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH 3/5] ext4: Convert to generic reserved quota's space management. [V5]
Date: Mon, 14 Dec 2009 09:32:50 -0500 [thread overview]
Message-ID: <20091214143250.GB4867@thunk.org> (raw)
In-Reply-To: <1260793276-8511-3-git-send-email-dmonakhov@openvz.org>
BTW, for some reason this patches never made it to the linux-ext4
list. I'm not sure why; it's listed on the CC list, but it didn't
show up in the linux-ext4 archive, and it didn't show up in the
linux-ext4 patch queue. Doesn't matter, since Jan will probably need
to push the patch since it's dependant on changes in the generic quota
tree.
- Ted
next prev parent reply other threads:[~2009-12-14 14:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 12:21 [PATCH 1/5] Add unlocked version of inode_add_bytes() function Dmitry Monakhov
2009-12-14 12:21 ` [PATCH 2/5] quota: decouple fs reserved space from quota reservation. [V5] Dmitry Monakhov
2009-12-14 12:21 ` [PATCH 3/5] ext4: Convert to generic reserved quota's space management. [V5] Dmitry Monakhov
2009-12-14 12:21 ` [PATCH 4/5] quota: Move duplicated code to separate functions Dmitry Monakhov
2009-12-14 12:21 ` [PATCH 5/5] quota: handle IO errors in dquot_transfer() Dmitry Monakhov
2009-12-14 18:41 ` Jan Kara
2009-12-14 22:43 ` Dmitry Monakhov
2009-12-15 11:49 ` Jan Kara
2009-12-14 18:00 ` [PATCH 4/5] quota: Move duplicated code to separate functions Jan Kara
2009-12-14 14:32 ` tytso [this message]
2009-12-14 14:35 ` [PATCH 3/5] ext4: Convert to generic reserved quota's space management. [V5] tytso
2009-12-14 17:26 ` Jan Kara
2009-12-14 17:25 ` Jan Kara
2009-12-14 17:24 ` [PATCH 2/5] quota: decouple fs reserved space from quota reservation. [V5] Jan Kara
2009-12-14 17:21 ` [PATCH 1/5] Add unlocked version of inode_add_bytes() function Jan Kara
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=20091214143250.GB4867@thunk.org \
--to=tytso@mit.edu \
--cc=dmonakhov@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 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.