From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>,
Alex Tomas <alex@clusterfs.com>,
Andreas Dilger <adilger@clusterfs.com>
Subject: Re: Review of mballoc-core.patch
Date: Thu, 27 Sep 2007 21:34:14 +0530 [thread overview]
Message-ID: <46FBD47E.2060205@linux.vnet.ibm.com> (raw)
In-Reply-To: <E1Iauxj-0001fp-F4@candygram.thunk.org>
Theodore Ts'o wrote:
> Here's an initial code review of the mballoc-core.patch. As far as I
> can tell, the patch sent by Aneesh doesn't address any of these.
> Aneesh, assuming that you'll be fixing these, could you please combine
> your last set of fixes with fixes to address these, and send out an
> updated mballoc-core.patch?
Will do that
>Patches on top of patches are useful for
> seeing what has changed, but for the patch queue I'd like to get the
> patches folded into a single patch, since that's what we'd want to have
> placed into the git tree.
>
That is what i did with my last update. The diff of the source was sent to
the mailing list and and updated mballoc-core.patch was put at www.radian.org
so that we can use the same to update the patch queue. The diff against mballoc.c
helps in reviewing the changes made.
> Thanks!!
>
> - Ted
>
[.. snip...]
>
>
> There are a bunch of FIXME's in this which I assume will get addressed
> before we consider this ready to push to mainline?
>
I have updated the code with your suggestion. I haven't resolved all the
questions. The rest are marked with FIXME in the source. The idea is this
will help Alex to find easily the portion of the code that needs his immediate
attention.
-aneesh
prev parent reply other threads:[~2007-09-27 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 15:07 Review of mballoc-core.patch Theodore Ts'o
2007-09-27 16:04 ` Aneesh Kumar K.V [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=46FBD47E.2060205@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=adilger@clusterfs.com \
--cc=alex@clusterfs.com \
--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 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).