linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jing zhang <zj.barak@gmail.com>
To: tytso@mit.edu
Cc: "Aneesh Kumar K. V" <aneesh.kumar@linux.vnet.ibm.com>,
	linux-ext4 <linux-ext4@vger.kernel.org>,
	Andreas Dilger <adilger@sun.com>,
	Dave Kleikamp <shaggy@linux.vnet.ibm.com>
Subject: Re: [PATCH] ext4: memory leakage in ext4_mb_init()
Date: Sun, 4 Apr 2010 09:05:14 +0800	[thread overview]
Message-ID: <j2tac8f92701004031805s9b09d04csc5adf5199dc9b9a7@mail.gmail.com> (raw)
In-Reply-To: <20100403165340.GA17819@thunk.org>

2010/4/4, tytso@mit.edu <tytso@mit.edu>:
> Hi Jing,
>
> If you're wondering why I'm taking a long time to respond to your
> patches, it is because they are very ill-formed.  They don't conform
> to the submitting patches guidelines, the patch comments don't
> adequately explain the why the patch is needed, and what testing has
> been done, and you tend to throw in patches that aren't correctly
> submitted in the middle of comments, and in some cases it's not clear
> whether this patch is suppose to be in addition to the previous patch,
> and combined into a separate commit, or kept as two separate patches,
> etc.
>

Sorry again, Ted.

There are so much for a newbie to learn to do cool work, especially to
meet your requirements. I am happy, any way, to patch ext4 under your
direction.

> As a result, it takes, much, MUCH, MUCH longer for me to review the
> patches for correctness.  I will eventually get to them, but I may end
> up working on other patches which are better formed and easier for me
> to evaluate for correctness and quality.
>
> If you do submit new patches, especially in this thread where you have
> already submitted so many different patches, I would appreicate it if
> you could explicitly state that a particular patch has been superceded

Without the cool git, though I am learning how to take advantage of
it, I could not manage all the patches delivered. In fact, I dig the
patches with UltraEdit for modifying the C code, Cygwin for git and
diff -Npu, and virtual machine for compiling. My kid, 11 years old
boy, has to share the HP notebook with me playing games.

And please laugh at me, I am not living in stone age.

I resolve conflicts and dependencies between patches in the way that
they are carried out by independent guys, since I am told that git is
cool enough. But indeed I created so many hard work for you, sorry.

Is it possible for me to patch not based upon the stock version I
downloaded at kernel.org, but upon the patched version, say the latest
git tree?


> by another, or has been withdrawn.  I will try to keep score on the
> patchwork web site (for example, I rejected your bb_free_cache patch),
> but you've been so prolific with patches, some of which haven't been
> very well explained, that I may have lost track of all of your
> submissions.
>
> Please bear with me.

No problem. I like ext4, maybe still the native file system of GNU
Linux, and the cool guys such as Alen Cox, Andy Clin, Ingo Molnar,
Rusty Russell, Jens Axboe, Alexey N. Kuznetsov (where r u now, ANK?),
Mike Haertel, Avi Kivity, Ted, Reiser, and their cool works which help
many newbies to understand Linux, to apply the cool ideas and methods
they learned in Linux to their everyday work, to earn bread and salt
in this hard time.

One of the amazing cools of Linux, I believe, besides free, is to
change ideas and lives of individuals, and to change what should be
changed in the society in which individuals live.

I am being changed to do patch in appreciated way.

Thanks
               - zj

>
> Best regards,
>
> 					- Ted

  reply	other threads:[~2010-04-04  1:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-21 14:01 [PATCH] ext4: memory leakage in ext4_mb_init() jing zhang
2010-03-22  1:27 ` tytso
2010-03-23 12:47   ` jing zhang
2010-03-26  8:57     ` Aneesh Kumar K. V
2010-03-26 14:40       ` jing zhang
2010-03-28  8:13       ` jing zhang
2010-04-03 16:53         ` tytso
2010-04-04  1:05           ` jing zhang [this message]
2010-04-04 18:08             ` tytso
2010-04-05  3:53               ` jing zhang
2010-04-05  4:27                 ` Eric Sandeen
2010-04-05  4:51                   ` jing zhang
2010-04-05  4:59                     ` Eric Sandeen
2010-04-05  5:08                       ` jing zhang
2010-04-05 12:42                         ` tytso
2010-04-06 13:43                           ` jing zhang
2010-04-06 14:21                             ` tytso
2010-04-07 16:34                               ` jing zhang
2010-04-05  5:18                       ` jing zhang
2010-04-05 12:43                         ` tytso
2010-03-26  8:54 ` Aneesh Kumar K. V

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=j2tac8f92701004031805s9b09d04csc5adf5199dc9b9a7@mail.gmail.com \
    --to=zj.barak@gmail.com \
    --cc=adilger@sun.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=shaggy@linux.vnet.ibm.com \
    --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).