From: Andrew Perepechko <Andrew.Perepechko@Sun.COM>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org,
Johann Lombardi <Johann.Lombardi@Sun.COM>,
Zhiyong Landen tian <Zhiyong.Tian@Sun.COM>
Subject: Re: [PATCH] quota: additional range checks and mem_dqblk updates?to handle 64-bit limits
Date: Thu, 13 Mar 2008 01:35:02 +0300 [thread overview]
Message-ID: <200803130135.02875.andrew.perepechko@sun.com> (raw)
In-Reply-To: <20080312172119.GA21395@duck.suse.cz>
Hello, Jan!
Thank you very much, first of all.
I'm going to update the patch with respect to your considerations ASAP.
Andrew.
On Wednesday 12 March 2008 20:21:19 Jan Kara wrote:
> Hello Andrew,
>
> below is the patch I've ended with. I've removed the modification of
> mem_dqblk, so that the patch is a bugfix only (structure if_dqblk is able
> to keep 64-bit values already). I'll push this patch to Andrew, for
> inclusion.
> Also after some thinking I like the idea of 64-bit quota format so please
> send me the final patch based on the patch below when you have it ready and
> I'll include it as well.
>
> Honza
prev parent reply other threads:[~2008-03-12 22:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-07 0:29 [PATCH] quota: additional range checks and mem_dqblk updates to handle 64-bit limits Andrew Perepechko
2008-03-07 16:00 ` Jan Kara
2008-03-07 21:10 ` Andreas Dilger
2008-03-10 14:54 ` Jan Kara
2008-03-08 0:56 ` Andrew Perepechko
2008-03-10 15:20 ` [PATCH] quota: additional range checks and mem_dqblk updates?to " Jan Kara
2008-03-10 22:46 ` Andrew Perepechko
2008-03-11 3:16 ` Zhiyong Landen tian
2008-03-10 16:28 ` [PATCH] quota: additional range checks and mem_dqblk updates to " Jan Kara
2008-03-10 21:25 ` Andrew Perepechko
2008-03-12 17:21 ` [PATCH] quota: additional range checks and mem_dqblk updates?to " Jan Kara
2008-03-12 22:35 ` Andrew Perepechko [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=200803130135.02875.andrew.perepechko@sun.com \
--to=andrew.perepechko@sun.com \
--cc=Johann.Lombardi@Sun.COM \
--cc=Zhiyong.Tian@Sun.COM \
--cc=jack@suse.cz \
--cc=linux-fsdevel@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).