From: Jan Kara <jack@suse.cz>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: Jan Kara <jack@suse.cz>, linux-ext4@vger.kernel.org, tytso@mit.edu
Subject: Re: writev corruption and 64-bit quota patches for 2.6.33-rc1?
Date: Wed, 9 Dec 2009 11:08:38 +0100 [thread overview]
Message-ID: <20091209100837.GA4863@quack.suse.de> (raw)
In-Reply-To: <87ein5bdpu.fsf@openvz.org>
Hi,
On Tue 08-12-09 20:03:09, Dmitry Monakhov wrote:
> Jan Kara <jack@suse.cz> writes:
> > Hi Ted,
> >
> > do you plan on merging my fixes for writev filesystem corruption and
> > 64-bit quota patches? The writev patch is independent of any other patch
> > and should go in ASAP, 64-bit quota patch depends on generic quota code
> BTW, where can I find this changes for generic quota code.
> Your linux-quota-2.6.git disappeared from kernel.org couple weeks ago,
> so I can't find in anywhere.
There's linux-fs-2.6.git which now carries also the quota changes (they
are scarce enough that I've decided to merge quota tree into my
linux-fs-2.6 tree).
Honza
next prev parent reply other threads:[~2009-12-09 10:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 11:00 writev corruption and 64-bit quota patches for 2.6.33-rc1? Jan Kara
2009-12-08 17:03 ` Dmitry Monakhov
2009-12-09 10:08 ` Jan Kara [this message]
2009-12-08 21:21 ` tytso
2009-12-09 10:58 ` 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=20091209100837.GA4863@quack.suse.de \
--to=jack@suse.cz \
--cc=dmonakhov@openvz.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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.